on last UBUNTU 18.4.1 cannot set max CPU time to be used

Message boards : Questions and problems : on last UBUNTU 18.4.1 cannot set max CPU time to be used
Message board moderation

To post messages, you must log in.

AuthorMessage
lucaaah

Send message
Joined: 18 Sep 18
Posts: 1
Italy
Message 88120 - Posted: 18 Sep 2018, 23:00:53 UTC

After upgrading to latest UBUNTU version 18.4.1, on every machine i try using BOINC-manager to open the window for "options" and later "computing preferences" required to set max CPU load (to avoid overheating of quad core CPU), the windows opens but it is just WHITE: no more options visible to set CPU load limit.
The faulty ubuntu is the last version available in Italy.
Is there a command-line program i could use to set it? Is there any config file i could manually change by editing it? Thank you
ID: 88120 · Report as offensive
Profile Dave
Help desk expert

Send message
Joined: 28 Jun 10
Posts: 2539
United Kingdom
Message 88122 - Posted: 19 Sep 2018, 6:52:46 UTC

For me, the best way to do this is to limit the number of cpu's rather than percentage of cpu time. Pretty sure there is an option in cc_config.xml to do this. Despite the xml extension of this file, edit in a text editor and save as a plain text file.

The option you are looking for is I think
<ncpus>N</ncpus>
Act as if there were N CPUs; e.g. to simulate 2 CPUs on a machine that has only 1. To use the number of available CPUs, set the value to -1 (was 0 which in newer clients really means zero).


So if you set it to three it will be the same as restricting BOINC to 75% of cpu's using BOINC Manager.

If I have got this wrong someone will be sure to give the correct version shortly.
ID: 88122 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 88124 - Posted: 19 Sep 2018, 7:24:16 UTC - in response to Message 88120.  

When every screen is white, it means that you only started the manager, not the client. Under Linux starting BOINC Manager won't start the client, you have to start it (boinc-client) separately and prior to the manager.

When the computing options screen is white, it would seem that BOINC Manager - or part thereof - is missing something to render it completely. What you can try is to do an <code>ls boinc-manager</code> from a terminal window. That's El Es. If you can't read it all, copy & paste it here and a Linux guru will probably be able to tell you if something's missing and needed.

Don't use the cc_config.xml file to set the amount of CPU cores. That option is used for testing, and is primarily for running work on more cores than you have. So you can for instance set it to 64 on a 4 core CPU and run 64 tasks (slowly, because the 4 cores will run all 64 at the same time, 16 per core)

If you want to hand edit any file, edit global_prefs_override.xml, and then the max_ncpus_pct value. Do know it's percentages that are used here.
ID: 88124 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 88127 - Posted: 19 Sep 2018, 7:45:01 UTC - in response to Message 88124.  

If you want to hand edit any file, edit global_prefs_override.xml, and then the max_ncpus_pct value. Do know it's percentages that are used here.
That's what setting preferences via the BOINC Manager interface does: it creates an override file (which is optional and may not be present on your machine), and thus detaches you from the alternative method of setting preferences via a project web site. Check the Event Log after startup to see whether the line

18-Sep-2018 17:42:36 [---] Reading preferences override file
is present. If it is, edit it: if not, edit your global preference set on a project web site.

As Dave says, it's usually better to change the first preference ("Use at most nnn% of the CPUs"), rather than fiddling with CPU time.
ID: 88127 · Report as offensive

Message boards : Questions and problems : on last UBUNTU 18.4.1 cannot set max CPU time to be used

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.