In preparation for "the launch",we are currently experimenting with validator settings. This will cause an artificially high rate of invalid results in the next few hours, but this allows us to collect some important data. So nothing to worry about :-)
I have my older task done but it is still running. On trying to save all Messages to Memory to dump them BM is hanging again. Will report via Alpha Email list.
I don't understand.
With 1.23 version i have the strange "stop and go" behavior.
Now with 1.24, another problem.....
With version 1.23, my 4-core cpu runs 3 wu cpu of another project and 1 gpu wu of A@H on my gpu card, now the A@H gpu indicates the use of 0.95cpu, but i run 4 cpu wu and the gpu wu is VERY slow (40% after 5h). If i crunch only 3 cpu wu (suspend others), the wu gpu accelerates and finish very fast.
I try to restart client, but nothing changes.
I don't use xml configuration file.
I don't know if this is a BM thing or albert app thing.
But the downloaded tasks shows an estimated runtime of 20hours and they all get done with about 1-2hours.
I use BM 7.0.27
All other projects adjust as they should....Except POEM@Home that sometimes show strangly numbers....
Have I run to few tasks??
I am now running 1 albert task on my ati 5850 with 0.932cpu and 1 seti ap task on the same gpu
I also noticed 2 cpu tasks running at the same time on my 2 cores.
1 of the cpu projects runs fully on 1 core and the other cpu project runs on the albert core with 0.1 cpu
I cannot be sure that the cpu cores use different cores though...
I lack the knowlegde in how to pursue the threads.
My conclusion is that I know have 1 cpu project running with 0.1 cpu on the same core that feeds the GPU for albert.
Any chance if this is correct that you can free some more % from albert task that runs? Albert only uses below 50% of 1 cpu core.
I cannot be sure that the cpu cores use different cores though...
I lack the knowlegde in how to pursue the threads.
Your operating system's scheduler should take care of this unless you force specific applications to use specific cores. Basically the way it works is that applications/threads get 'time slices' from the OS scheduler, which is how it can run multiple applications side by side on a single core. Between time slices the scheduler might decide to continue to run a thread on a different core depending on how busy each core is - that's why you generally see even single-threaded applications using a bit of each core: because they spend about equal time running on each one.
Hardware: Desktop-GPU, ATI Radeon HD5450, 1024 MB DDR3, (650/800Mhz)
Software: Catalst 12.3, BOINC 7.0.26 (x64), Windows 7/64 RAM-Usage: Taskmanager during GPU-process: ~207 MB (max) no visible GPU-Usage (by AMD Overdrive), computing the workunits took just same seconds until fail Each workunit failed, so I stopped processing.
New day, new test: it´s running !
RAM-usage System: 208 MB RAM max., 84 MB at the moment
GPU: 43 percent usage with (4,596 CPUs + 1 ATI GPU)
GPU: 95 percent usage with (3,596 CPUs + 1 ATI GPU)
GPU Temp: 50 stock, 65 degrees @Albert@home
estimated runtime for the Albert-Workunit: 24 hours, dead line in 14 days.
It runs slowly, but with noticeable lags @95 percent GPU usage. CPU usage in BOINC is suboptimal with 3,596 CPUs.
I must add this: When
)
I must add this:
When running a cpu project on 1 core and albert gpu task starts then the cpu project goes into "waiting to run state".
Any chance that you can make albert GPU task work so it is a GPU task and not as it is now a cpu task??
Hi all, In preparation for
)
Hi all,
In preparation for "the launch",we are currently experimenting with validator settings. This will cause an artificially high rate of invalid results in the next few hours, but this allows us to collect some important data. So nothing to worry about :-)
Cheers
HB
I have my older task done but
)
I have my older task done but it is still running. On trying to save all Messages to Memory to dump them BM is hanging again. Will report via Alpha Email list.
Christoph
I don't understand. With 1.23
)
I don't understand.
With 1.23 version i have the strange "stop and go" behavior.
Now with 1.24, another problem.....
With version 1.23, my 4-core cpu runs 3 wu cpu of another project and 1 gpu wu of A@H on my gpu card, now the A@H gpu indicates the use of 0.95cpu, but i run 4 cpu wu and the gpu wu is VERY slow (40% after 5h). If i crunch only 3 cpu wu (suspend others), the wu gpu accelerates and finish very fast.
I try to restart client, but nothing changes.
I don't use xml configuration file.
I don't know if this is a BM
)
I don't know if this is a BM thing or albert app thing.
But the downloaded tasks shows an estimated runtime of 20hours and they all get done with about 1-2hours.
I use BM 7.0.27
All other projects adjust as they should....Except POEM@Home that sometimes show strangly numbers....
Have I run to few tasks??
I am now running 1 albert
)
I am now running 1 albert task on my ati 5850 with 0.932cpu and 1 seti ap task on the same gpu
I also noticed 2 cpu tasks running at the same time on my 2 cores.
1 of the cpu projects runs fully on 1 core and the other cpu project runs on the albert core with 0.1 cpu
I cannot be sure that the cpu cores use different cores though...
I lack the knowlegde in how to pursue the threads.
My conclusion is that I know have 1 cpu project running with 0.1 cpu on the same core that feeds the GPU for albert.
Any chance if this is correct that you can free some more % from albert task that runs? Albert only uses below 50% of 1 cpu core.
RE: I cannot be sure that
)
Your operating system's scheduler should take care of this unless you force specific applications to use specific cores. Basically the way it works is that applications/threads get 'time slices' from the OS scheduler, which is how it can run multiple applications side by side on a single core. Between time slices the scheduler might decide to continue to run a thread on a different core depending on how busy each core is - that's why you generally see even single-threaded applications using a bit of each core: because they spend about equal time running on each one.
RE: Hardware: Desktop-GPU,
)
New day, new test: it´s running !
RAM-usage System: 208 MB RAM max., 84 MB at the moment
GPU: 43 percent usage with (4,596 CPUs + 1 ATI GPU)
GPU: 95 percent usage with (3,596 CPUs + 1 ATI GPU)
GPU Temp: 50 stock, 65 degrees @Albert@home
estimated runtime for the Albert-Workunit: 24 hours, dead line in 14 days.
It runs slowly, but with noticeable lags @95 percent GPU usage. CPU usage in BOINC is suboptimal with 3,596 CPUs.
These wu's show BRPCUDA32
)
These wu's show BRPCUDA32 v1.25 throwing errors:
http://albertathome.org/workunit/69412
http://albertathome.org/workunit/70631
http://albertathome.org/workunit/70986
http://albertathome.org/workunit/71008
Most of which are from the same host (GTX 480), with one from this host (GTX285).
Also, the BRPSSE3 v1.22 client is throwing errors:
http://albertathome.org/workunit/70871
http://albertathome.org/workunit/70837
(from the same host)
So, finally catched a running
)
So, finally catched a running task. HD5450 1gb memory max workgroup 128.
Memory use as per GPU-Z: 416 dedicated, around 70 dynamic. GPU load 96%
Christoph