If BOINC is using GetSystemInfo() function to find the number of logical processors in the computer
I think BOINC will see no more than 64 CPUs.

I hope the workaround will be to set in cc_config.xml

   <options>
      <ncpus>160</ncpus>
   </options>

(this was proposed already in the second post in this thread)

I'm not sure will the 160 running tasks be properly assigned to different logical CPUs or will run in just a group of 64 CPUs.

That just tells BOINC to run that number of instances of the science app IIRC. Windows SHOULD take care of assigning resources correctly.

EDIT: ncpus defiantly works
3/9/2011 8:24:57 PM Processor: 256 GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz [Family 6 Model 30 Stepping 5]
Also if you do not have 256 cpu's make sure you suspend running work before setting that & running BOINC. As trying to run 16 threads per cpu on a wee i7 with only 4GB of ram isn't a good thing. lol
3/9/2011 8:29:23 PM Number of usable CPUs has changed from 256 to 8. Running benchmarks. Phew!

I did just fire up with Superdome 2. Which is 64 socket and 256LP IA-64. I am running about 12% resources and its not scaling so far like the smaller 4 socket.

---

it thinks its a 32 CPU. LOL

---

If BOINC is using GetSystemInfo() function to find the number of logical processors in the computer
I think BOINC will see no more than 64 CPUs.

I hope the workaround will be to set in cc_config.xml

   <options>
      <ncpus>160</ncpus>
   </options>

(this was proposed already in the second post in this thread)

I'm not sure will the 160 running tasks be properly assigned to different logical CPUs or will run in just a group of 64 CPUs.

That just tells BOINC to run that number of instances of the science app IIRC. Windows SHOULD take care of assigning resources correctly.

EDIT: ncpus defiantly works
3/9/2011 8:24:57 PM Processor: 256 GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz [Family 6 Model 30 Stepping 5]
Also if you do not have 256 cpu's make sure you suspend running work before setting that & running BOINC. As trying to run 16 threads per cpu on a wee i7 with only 4GB of ram isn't a good thing. lol
3/9/2011 8:29:23 PM Number of usable CPUs has changed from 256 to 8. Running benchmarks. Phew!

I did just fire up with Superdome 2. Which is 64 socket and 256LP IA-64. I am running about 12% resources and its not scaling so far like the smaller 4 socket.


[ img ]http://i251.photobucket.com/albums/gg287/bryananddaun/superdome2.jpg[ /img ]

Can you try <ncpus>128</ncpus> in a cc_config.xml and see if it uses 128 of the processors? I have a feeling that there might be limits set per user on the servers you are using.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

If BOINC is using GetSystemInfo() function to find the number of logical processors in the computer
I think BOINC will see no more than 64 CPUs.

I hope the workaround will be to set in cc_config.xml

   <options>
      <ncpus>160</ncpus>
   </options>

(this was proposed already in the second post in this thread)

I'm not sure will the 160 running tasks be properly assigned to different logical CPUs or will run in just a group of 64 CPUs.

Thanks, I set this on the 256 way. lets see what happens.

3/9/2011 5:58:36 PM SETI@home suspended by user
3/9/2011 5:58:41 PM Re-reading cc_config.xml
3/9/2011 5:58:41 PM Re-read config file
3/9/2011 5:58:41 PM Config: use at most 256 CPUs
3/9/2011 5:58:41 PM log flags: file_xfer, sched_ops, task, sched_op_debug
3/9/2011 5:58:41 PM Number of usable CPUs has changed from 32 to 256. Running benchmarks.
3/9/2011 5:58:41 PM Running CPU benchmarks
3/9/2011 5:58:42 PM Suspending computation - running CPU benchmarks
3/9/2011 5:58:55 PM Re-reading cc_config.xml
3/9/2011 5:58:55 PM Re-read config file
3/9/2011 5:58:55 PM Config: use at most 256 CPUs
3/9/2011 5:58:55 PM log flags: file_xfer, sched_ops, task, sched_op_debug

---

[quote]
If BOINC is using GetSystemInfo() function to find the number of logical processors in the computer
I think BOINC will see no more than 64 CPUs.

I hope the workaround will be to set in cc_config.xml

   <options>
      <ncpus>160</ncpus>
   </options>

(this was proposed already in the second post in this thread)

I'm not sure will the 160 running tasks be properly assigned to different logical CPUs or will run in just a group of 64 CPUs.

That helped, went from 12 to 26 on the 256 way. Ill try it on the X64 160 now.

---

[quote]
If BOINC is using GetSystemInfo() function to find the number of logical processors in the computer
I think BOINC will see no more than 64 CPUs.

I hope the workaround will be to set in cc_config.xml

   <options>
      <ncpus>160</ncpus>
   </options>

(this was proposed already in the second post in this thread)

I'm not sure will the 160 running tasks be properly assigned to different logical CPUs or will run in just a group of 64 CPUs.

That helped, went from 12 to 26 on the 256 way. Ill try it on the X64 160 now.

Actually that really helped!! Thanks.. We are aproaching 60% on the 256way IA-64 and 90%+ on the 160LP X64.

---

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

---

---

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

For the X64 160 LP box did you use <ncpus>160</ncpus> or a lower value?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

For the X64 160 LP box did you use <ncpus>160</ncpus> or a lower value?

I used the 160, its stable at 90-92% now

---

It will be really interesting to see how this experiment turns out Bryan.

We have many people running multiple core graphics cards to great success,
if you put 512 Shaders(graphics cores) together on 2-3 tasks they have some pretty amazing results. It will be quite interesting to see if your configuration gives them a run for the money.

---

Janice

Something that hasn't been mentioned yet:

The guys here are talking about CPU scaling for a Dell server, which led to the power management settings:

http://serverfault.com/questions/196301/disable-cpu-scaling-in-windows-server-2008-r2

and on that page below the blue banner, they mention HP's default setting ignores the OS setting.

Martin


edited ... Why ignore the OS settings? The Dell server setting (see above) was also preventing the expected server performance.

Interesting in deed. 64 threads on the cpu alone should prove to be a monster cruncher! Then throwing in some gpu's on top of that, it would be interesting to see how it stacks up against a quad gpu machine with dual processors for sure.

---

Traveling through space at ~67,000mph!

Most likely to keep heat, energy costs and reliability in check.

Cheers.

---

It will be really interesting to see how this experiment turns out Bryan.

We have many people running multiple core graphics cards to great success,
if you put 512 Shaders(graphics cores) together on 2-3 tasks they have some pretty amazing results. It will be quite interesting to see if your configuration gives them a run for the money.

Thanks! I know on the IA-64 side I probably wont be able to find a performance GPU driver so I will probably only be able to add them to the X64 side. If all goes well Ill try it tomorrow.

---

Something that hasn't been mentioned yet:

The guys here are talking about CPU scaling for a Dell server, which led to the power management settings:

http://serverfault.com/questions/196301/disable-cpu-scaling-in-windows-server-2008-r2

and on that page below the blue banner, they mention HP's default setting ignores the OS setting.

Martin


edited ... Why ignore the OS settings? The Dell server setting (see above) was also preventing the expected server performance.

They are dealing with Nehalem CPU's For IA-64 this wont apply but for my X64 160P system it does. Since I work for the company in question (HP) I have all the proper settings for ACPI, Power, C-states, K groups, X2APIC etc.. Spent several months on these with our firmware and perforance guys. Great catch thanks for posting!!

---

... 160 LP system not being able to scale properly. ...

You could check it out with Linux... That would make for a very interesting comparison! (Linux is designed to scale up well, especially for the scheduler.)

Linux..... barf... :) Sorry we are windows server users only. LOL

Not any more according to the latest news...


Good fun interesting testing there! Didn't know that Itanium systems were still being developed.

Shame there isn't a credit claimed RAC that was calculated on a host so that you could immediately see what rate of processing was being done, rather than waiting a month or so for the boinc server side RAC to glacially drift through its averaging... An instant RAC would make for much easier testing...


Good luck, and:

Happy fast crunchin'!,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

"I am starting to understand": Congratulations! You are the first ;)

AFAIK no one have experience running BOINC/SETI on so big number of CPUs,
you are exploring uncharted territories.


P.S.
I see you are using SSE3 app but I think your CPU
Intel(R) Xeon(R) CPU E7- 2870 @ 2.40GHz
supports SSSE3
http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon%20E7-2870%20AT80615007266AA.html

Rerun the Lunatics' Unified Installer and choose SSSE3 for faster/fastest app.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

"I am starting to understand": Congratulations! You are the first ;)

AFAIK no one have experience running BOINC/SETI on so big number of CPUs,
you are exploring uncharted territories.


P.S.
I see you are using SSE3 app but I think your CPU
Intel(R) Xeon(R) CPU E7- 2870 @ 2.40GHz
supports SSSE3
http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon%20E7-2870%20AT80615007266AA.html

Rerun the Lunatics' Unified Installer and choose SSSE3 for faster/fastest app.

Ahh on the X64 side, good catch. How exactly do I rerun the Lunatics' Unified Installer? Thanks in advance

---

Superdome 2 is SCALING!! 99%

X64 160 LP box is also at 90%!!!! 5 to 10 percent more would be awesome if anyone has ideas.

this is getting easier now that I am starting to understand what you guys are talking about and understanding the tool.

Thanks everyone!

I think tomorrow I might throw some nasty GPU's in the X64 160 LP box and see what happens. My new memory risers will also me in which will help performance.

"I am starting to understand": Congratulations! You are the first ;)

AFAIK no one have experience running BOINC/SETI on so big number of CPUs,
you are exploring uncharted territories.


P.S.
I see you are using SSE3 app but I think your CPU
Intel(R) Xeon(R) CPU E7- 2870 @ 2.40GHz
supports SSSE3
http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon%20E7-2870%20AT80615007266AA.html

Rerun the Lunatics' Unified Installer and choose SSSE3 for faster/fastest app.

Ahh on the X64 side, good catch. How exactly do I rerun the Lunatics' Unified Installer? Thanks in advance

Double click "Lunatics_Win64v0.37_(SSE3+)_AP505r409_AKv8bx64_Cudax32f.exe" or whichever version you have. :)

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[