Posts by Collin Sale

1) Questions and Answers : Preferences : Deleted Rosetta@Home because it is wasting my CPU-time (Message 94075)
Posted 10 Apr 2020 by Collin Sale
Post:
Why wouldn't 3 days be enough? The default Target CPU run time is 8 hours.

Well then we have a different idea about the BOINC project.
Maybe you should rename the project to -> "Rosetta@dedicated_PC_with_no_other_tasks_running" instead of "Rosetta@Home" where people are encouraged to use spare CPU cycles on their HomeComputers.

.. do you have BOINC set to suspend work while the computer is in use?

Yes, and this was never an issue and I completed far more than 90% of SETI@home and Asteroids@home.
climateprediction.net had the same issue with deadlines, but they don't put @Home in their name.
Is there a particular programme that is impacted by crunching? If so, you can set BOINC to stop crunching when that programm is in use, but keep working the rest of the time.
My system uses all cores & threads all the time with no impact on other programmes or system responsiveness.

Fusion360, SketchUp, Blender are all affected when BOINC takes all cores.

Just like Seti, and all other projects, it takes time for the Manager to get the Estimated processing time to match the actual time. With the longer running Tasks, it does take longer for them to adjust. And it's best to run with a small cache to avoid getting more work than you can handle when applications change or you get dodgy Tasks.


I would love to see the statistics how many packages need to be shipped to clients more than once!
And I guess you would have more throughput if you'd just extend the deadline.

Honestly, on machines that crunch 24/7 a longer deadline does not harm anyone at all.
On "SinglePC-Owners"-side, you could gain more results without having to ship the packages again.

Computing
   Usage limits	
        Use at most 75% of the CPUs
        Use at most 80% of CPU time -> to keep 'snappyness'

   When to suspend	
        Suspend when computer is on battery (selected)
        Suspend when computer is in use (not selected)
        Suspend GPU computing when computer is in use (not selected)
        'In use' means mouse/keyboard input in last 1 minutes
        Suspend when no mouse/keyboard input in last --- minutes
        Suspend when non-BOINC CPU usage is above 60 %
        Compute only between ---

   Other	
        Store at least 1 days of work
        Store up to an additional 1 days of work
        Switch between tasks every 60 minutes
        Request tasks to checkpoint at most every 30 seconds

   Disk
        Use no more than 5 GB
        Leave at least 50 GB free
        Use no more than 10 % of total

   Memory
        When computer is in use, use at most 50 %
        When computer is not in use, use at most 90 %
        Leave non-GPU tasks in memory while suspended (selected)
        Page/swap file: use at most 50 %


Best Regards
2) Questions and Answers : Preferences : Deleted Rosetta@Home because it is wasting my CPU-time (Message 94063)
Posted 10 Apr 2020 by Collin Sale
Post:
Seti@Home:
Final data is in the splitter queue.
As promised, we've stopped the process that puts new data into the queue

I thought I would try Rosetta once again.
Actually it got worse than better.
Just downloaded the first Package and it has a deadline on Apr 13.
So if a week wasn't enough, let's try with 3 days!!

Since I downloaded it, I will keep this task alive.
But I already set BOINC to not download another package.
Created Screenshots of all Settings but I cannot upload to this Forum and I've got no WebSpace to put the images :-/

Curious if I will able to complete the package in time. There is a 97% chance that I will not, due to the normal usage of the mac.
Best Regards
3) Questions and Answers : Preferences : Deleted Rosetta@Home because it is wasting my CPU-time (Message 88932)
Posted 18 May 2018 by Collin Sale
Post:
Rosetta workloads are far bigger than for Instance Seti.
The Workload that was downloaded took up more space as I reserved for Boinc, so it blocked all other incoming packages!

Also, the workloads I get are only valid for a week and each package takes more than 8 hours of calculation. This is completely unrealistic.

Seti offers an 8-week timespan for a 2h workload.
In Comparison Rosetta would need to extend their period by adding 15-times the amount of time for the load to be finished.

The project just deleted over 40hours of work done, due to the limited timespan until the deadline.

So not only is Rosetta blocking other projects by exceeding the disk-quota, it is also a pure waste of my CPU if I get unrealistic deadlines.

Would have loved to support,
but if every item I receive goes to another PC once I'm 80% finished, it is no use to participate at all.

No offense, I might try again some time
Best Regards
Robin






©2024 University of Washington
https://www.bakerlab.org