Message boards : Number crunching : Max # jobs and Max # CPUs
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jun 08
Posts: 1453
Credit: 77,390,430
RAC: 92,768
Message 40972 - Posted: 16 Dec 2019, 7:23:05 UTC - in response to Message 40969.  

The core 2 duo only has 4 gb, but is also running Linux. Should that be okay with Atlas too?

It may run if the machine isn't too busy with other work. Just try it out.


Is there a quick method to downgrade to an earlier version?

If you encounter problems running BOINC 7.16.3 you may
- run your buffers dry
- uninstall 7.16.3
- install a different version, e.g. 7.14.2.



...machines with half the ram I should set an alternative profile with CPU cores set to 2...

On a 16MB machine ATLAS native should run either as 1-core or as 2-core.
If you prefer shorter total runtimes you may use the 2-core setup on both machines.
Administration becomes easier if you use the same setup on all machines (if possible).


... does not have virtualization able to be selected in the bios. Does native in Linux allow one not to have that running and still get by, or does it need to be enabled even if you're not using virtual box?

BIOS/CPU virtualization must be enabled to run LHC VirtualBox tasks.
Native tasks don't require VirtualBox, hence they don't care about BIOS virtualization.


... do I need to install additional packages under virtual box or is that just to be able to view the current VM status?

... to view the current VM status .


Under Linux most of my machines are headless so this would be pointless?

You may setup remote connections to your headless computers and control/monitor them from your desktop.
In this case you would miss something if guest additions are not installed.
ID: 40972 · Report as offensive     Reply Quote
Henry Nebrensky

Send message
Joined: 13 Jul 05
Posts: 119
Credit: 13,413,113
RAC: 5,097
Message 40974 - Posted: 16 Dec 2019, 9:50:37 UTC - in response to Message 40965.  

I don't think anyone answered one of your questions:

... on the single little core 2 duo I have running on here, if there was an Asteroids at home task running, and boinc decided a native theory Atlas task should start, with max number of jobs CPUs set to 2, there would be 2 theory Atlas tasks using 0.5 CPUs (sharing one core) and asteroids would use the second if max CPUs was also set to 2. Am I understanding this correctly …?
No - the number of CPUs to be used by an (Atlas, either native or VBox) task is specified by that setting and then passed as a requirement down the chain. So if you set it to 2, the client will have to set aside two cores for it, and will therefore either wait until your Asteroids task has finished leaving the other core idle, or else find another single-core job (e.g. Sixtrack) to do in the meantime which won't finish at the same time and the cycle restarts...

So it's best not to set #CPUs to completely fill the machine, unless you dedicate it to only running Atlas. (In which case you also have to remember to untick the "If no work for selected applications is available, accept work from other applications?" box!)
ID: 40974 · Report as offensive     Reply Quote
Toby Broom
Volunteer moderator

Send message
Joined: 27 Sep 08
Posts: 598
Credit: 373,581,312
RAC: 42,350
Message 40983 - Posted: 17 Dec 2019, 12:29:16 UTC

I can see something has changed with ATLAS sliced computers, I can see on one it's got 12 running and 10 buffered on one computer and another 2 have 1 in buffer with 12 running on 12 simulated cores.

I'll try to run all the projects on one session of Boinc to see if ATLAS and the other project will work together when Max # jobs = No Limit and CPU = 1
ID: 40983 · Report as offensive     Reply Quote
Toby Broom
Volunteer moderator

Send message
Joined: 27 Sep 08
Posts: 598
Credit: 373,581,312
RAC: 42,350
Message 41013 - Posted: 19 Dec 2019, 10:38:38 UTC

It looks like it working fine. The schedule prioritizes SixTrack so unless I disable SixTrack the computer will just queue up all these tasks. If I disable SixTrack then it got a mix of Theory, CMS & ATLAS.
ID: 41013 · Report as offensive     Reply Quote
wolfman1360

Send message
Joined: 17 Feb 17
Posts: 16
Credit: 119,862
RAC: 0
Message 41037 - Posted: 23 Dec 2019, 20:48:53 UTC - in response to Message 40974.  

I don't think anyone answered one of your questions:

... on the single little core 2 duo I have running on here, if there was an Asteroids at home task running, and boinc decided a native theory Atlas task should start, with max number of jobs CPUs set to 2, there would be 2 theory Atlas tasks using 0.5 CPUs (sharing one core) and asteroids would use the second if max CPUs was also set to 2. Am I understanding this correctly …?
No - the number of CPUs to be used by an (Atlas, either native or VBox) task is specified by that setting and then passed as a requirement down the chain. So if you set it to 2, the client will have to set aside two cores for it, and will therefore either wait until your Asteroids task has finished leaving the other core idle, or else find another single-core job (e.g. Sixtrack) to do in the meantime which won't finish at the same time and the cycle restarts...

So it's best not to set #CPUs to completely fill the machine, unless you dedicate it to only running Atlas. (In which case you also have to remember to untick the "If no work for selected applications is available, accept work from other applications?" box!)

Thanks for this. Sorry for the late reply.
I've got a few questions before I actually migrate all my hosts over here that I'll throw up in a separate thread. I think I have most of them figured out, but reading through the forums is still leaving a few questions unanswered, in particular the network and bandwidth aspect.
ID: 41037 · Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Number crunching : Max # jobs and Max # CPUs


©2020 CERN