Thread 'Request: Add'l Multiprocessor Settings'

Message boards : BOINC client : Request: Add'l Multiprocessor Settings
Message board moderation

To post messages, you must log in.

AuthorMessage
contalis

Send message
Joined: 9 Dec 05
Posts: 35
United States
Message 3513 - Posted: 15 Mar 2006, 14:21:36 UTC

With the increase in multi-core processors (and computers on an network having various numbers of processors), it would be nice to have a setting:

1) When multi-processor computer is in use, use all but X processors (but no less than 1)
2) When multi-processor computer is not in use, use all but Y processors (but no more than Z)
ID: 3513 · Report as offensive
wumpus

Send message
Joined: 13 Feb 06
Posts: 9
United States
Message 3523 - Posted: 16 Mar 2006, 18:39:11 UTC

What is wrong with using the settings for using the computer only when idle? Are you having any specific problems you can explain? Why do you want this?
ID: 3523 · Report as offensive
Keck_Komputers
Avatar

Send message
Joined: 29 Aug 05
Posts: 304
United States
Message 3527 - Posted: 16 Mar 2006, 21:31:39 UTC

I can see the usefullness of having BOINC run on all processors when idle but leaving 1 (or more) for the user when they are doing something. I hope that a better description could be found if this was actually implemented though.
BOINC WIKI

BOINCing since 2002/12/8
ID: 3527 · Report as offensive
contalis

Send message
Joined: 9 Dec 05
Posts: 35
United States
Message 3528 - Posted: 16 Mar 2006, 23:39:23 UTC

Normally, setting BOINC to always run works fine. However, I've noticed certain applications get "jumpy". Configuring the settings to leave one processor free resolves the jumpiness while still allowing some processing to occur all the time.

A configuration as descibed below would be easier to administrate for a network of computers with varying numbers of processors.
ID: 3528 · Report as offensive

Message boards : BOINC client : Request: Add'l Multiprocessor Settings

Copyright © 2025 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.