Is there something wrong with my computer because my RAC keeps plummeting down like a meteor. I run Boinc on full throttle 24/7 but only get about 18 000 - 20 000 points per day now? At best times RAC was well above 50 000 daily.
Is there something wrong with my computer because my RAC keeps plummeting down like a meteor. I run Boinc on full throttle 24/7 but only get about 18 000 - 20 000 points per day now? At best times RAC was well above 50 000 daily.
Your computer was apparently doing BRP4G tasks earlier. There's no work left for that application anymore. It's replaced by FGRBP1G and 1.16 is current version on that application. Your host has some v1.15 tasks in queue, but I suggest you abort them because they are waste of time. New 1.16 and later versions will make your RAC grow again.
It's currently crunching multi directed continuous gravitational wave search CV 1.00 tasks and gamma ray pulsar binary search #1 on gpu's 1.16 (FGRPopenCL beta Nvidia) I deleted those 1.15 tasks.
Those CV 1.00 tasks took 20hrs to complete. Is that normal?
Those CV 1.00 tasks took 20hrs to complete. Is that normal?
I looked at your host and my amateurish estimate is that those CV 1.00 tasks might take that long if you run your system under very heavy load... close to 100%. How many tasks were you running parallel at that time?
If you want to run both GPU and CPU work at the same time (FGRPB1G and CV 1.00) I would personally setup your system to run perhaps 4 CPU tasks + 2 GPU tasks. Or with a cc_config.xml file you could lower the dedication factor of CPU per each GPU task to 0.5 CPU / 0.5 GPU (default is 1 CPU / 1 GPU) and then a nice combination might be 5 CPU + 2 GPU tasks. Others are better able to give advise on tweaking with that CPU factor... I haven't tried that kind of management thru the config file.
Most likely that's too much. It's generally a good idea to leave one or two threads/cores from those eight free, so it can dedicate its time to handle system operations. There's so much traffic that somebody needs to do it. That way the circus will start to fly.
Work is flowing again.
)
Work is flowing again.
Is there something wrong with
)
Is there something wrong with my computer because my RAC keeps plummeting down like a meteor. I run Boinc on full throttle 24/7 but only get about 18 000 - 20 000 points per day now? At best times RAC was well above 50 000 daily.
Eskomorko wrote:Is there
)
Your computer was apparently doing BRP4G tasks earlier. There's no work left for that application anymore. It's replaced by FGRBP1G and 1.16 is current version on that application. Your host has some v1.15 tasks in queue, but I suggest you abort them because they are waste of time. New 1.16 and later versions will make your RAC grow again.
Well, that explains the drop.
)
Well, that explains the drop. How to switch to FGRBP1G v 1.16?
The new work is automatically
)
The new work is automatically 1.16, just down load it.
It's currently crunching
)
It's currently crunching multi directed continuous gravitational wave search CV 1.00 tasks and gamma ray pulsar binary search #1 on gpu's 1.16 (FGRPopenCL beta Nvidia) I deleted those 1.15 tasks.
Those CV 1.00 tasks took 20hrs to complete. Is that normal?
Eskomorko wrote:Those CV 1.00
)
I looked at your host and my amateurish estimate is that those CV 1.00 tasks might take that long if you run your system under very heavy load... close to 100%. How many tasks were you running parallel at that time?
If you want to run both GPU and CPU work at the same time (FGRPB1G and CV 1.00) I would personally setup your system to run perhaps 4 CPU tasks + 2 GPU tasks. Or with a cc_config.xml file you could lower the dedication factor of CPU per each GPU task to 0.5 CPU / 0.5 GPU (default is 1 CPU / 1 GPU) and then a nice combination might be 5 CPU + 2 GPU tasks. Others are better able to give advise on tweaking with that CPU factor... I haven't tried that kind of management thru the config file.
It's running 8 tasks at same
)
It's running 8 tasks at same time. One per cpu.
Eskomorko wrote:It's running
)
Most likely that's too much. It's generally a good idea to leave one or two threads/cores from those eight free, so it can dedicate its time to handle system operations. There's so much traffic that somebody needs to do it. That way the circus will start to fly.
I eased the throttle a bit.
)
I eased the throttle a bit. We'll see, if it helped. It's now crunching down those FGRP wu's like a shredder :)