when is BURP going multicore? beyond 4...

Message boards : Number crunching : when is BURP going multicore? beyond 4...
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile xPOD
Avatar

Send message
Joined: 1 May 07
Posts: 56
Credit: 55,959,946
RAC: 0
Message 7290 - Posted: 4 Jan 2008, 12:24:08 UTC

as many of you know, I have some stout boxes but I can\'t seem to get BURP to run on all the CPU\'s - I believe it\'s how the program is setup to run - anyone have ideas as to when we\'ll have 8, 16 (or more) cores code available to run?
ID: 7290 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4544
Credit: 2,097,282
RAC: 193
Message 7292 - Posted: 4 Jan 2008, 13:04:52 UTC - in response to Message 7290.  
Last modified: 4 Jan 2008, 13:29:39 UTC

as many of you know, I have some stout boxes but I can\'t seem to get BURP to run on all the CPU\'s - I believe it\'s how the program is setup to run - anyone have ideas as to when we\'ll have 8, 16 (or more) cores code available to run?

It seems the BOINC peeps are pretty busy at the moment - at least these changes are slow at reaching them.
Instead I made the change locally. The scheduler now allows up to 2 workunits per CPU core (one running and one in uploading/downloading/reporting state).

Eventually this will reach the BOINC repository (I hope).
ID: 7292 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4544
Credit: 2,097,282
RAC: 193
Message 7293 - Posted: 4 Jan 2008, 13:28:06 UTC - in response to Message 7292.  

You should keep in mind, though, that some multicore systems are very likely to hit the memory bandwidth limit of the memory controller. It may be a good idea to mix low memory bandwidth projects (like seti?) with variable memory bandwidth projects like BURP (sometimes the sessions here require a lot of memory transfers, sometimes they don\'t).
ID: 7293 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile xPOD
Avatar

Send message
Joined: 1 May 07
Posts: 56
Credit: 55,959,946
RAC: 0
Message 7299 - Posted: 4 Jan 2008, 18:57:50 UTC - in response to Message 7292.  

as many of you know, I have some stout boxes but I can\'t seem to get BURP to run on all the CPU\'s - I believe it\'s how the program is setup to run - anyone have ideas as to when we\'ll have 8, 16 (or more) cores code available to run?

It seems the BOINC peeps are pretty busy at the moment - at least these changes are slow at reaching them.
Instead I made the change locally. The scheduler now allows up to 2 workunits per CPU core (one running and one in uploading/downloading/reporting state).

Eventually this will reach the BOINC repository (I hope).


how do you do this?
maybe we should have a BURP TUNING thread? :)
ID: 7299 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4544
Credit: 2,097,282
RAC: 193
Message 7300 - Posted: 4 Jan 2008, 19:05:27 UTC - in response to Message 7299.  
Last modified: 4 Jan 2008, 19:05:58 UTC

The scheduler now allows up to 2 workunits per CPU core (one running and one in uploading/downloading/reporting state).

how do you do this?
maybe we should have a BURP TUNING thread? :)

Oh it\'s the serverside scheduler, not the clientside one. So it should automatically work for you starting from the next session you receive.

And how did I do it? Change the server scheduler code, recompile, test, redeploy on alpha project. If something is wrong with it please let me know and I\'ll have a go at fixing it.
ID: 7300 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile xPOD
Avatar

Send message
Joined: 1 May 07
Posts: 56
Credit: 55,959,946
RAC: 0
Message 7301 - Posted: 4 Jan 2008, 19:19:44 UTC - in response to Message 7300.  

The scheduler now allows up to 2 workunits per CPU core (one running and one in uploading/downloading/reporting state).

how do you do this?
maybe we should have a BURP TUNING thread? :)

Oh it\'s the serverside scheduler, not the clientside one. So it should automatically work for you starting from the next session you receive.

And how did I do it? Change the server scheduler code, recompile, test, redeploy on alpha project. If something is wrong with it please let me know and I\'ll have a go at fixing it.


ok cool, so theoretically - on my 16-way servers - I could get 16 to process and 16 in pending/download/reporting?

no work currently so I can\'t really test it :)
ID: 7301 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4544
Credit: 2,097,282
RAC: 193
Message 7303 - Posted: 4 Jan 2008, 20:00:21 UTC - in response to Message 7301.  

ok cool, so theoretically - on my 16-way servers - I could get 16 to process and 16 in pending/download/reporting?

That\'s the idea, yes.

no work currently so I can\'t really test it :)

726 comming right up.
ID: 7303 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : when is BURP going multicore? beyond 4...