Now it’s happened =(, Ol’ Serpentor has stolen my no 1 slot, and I simply can’t crunch faster than I currently am (until they release a version which is optimized for XP64bit.
Congrats Serpentor, you truly deserve it. You were indeed a heavy cruncher for TeamBeOS as well so not more than right that you take what is yours.
Good job =)
Now it's happened =(, Ol' Serpentor has stolen my no 1 slot, and I simply can't crunch faster than I currently am (until they release a version which is optimized for XP64bit.Congrats Serpentor, you truly deserve it. You were indeed a heavy cruncher for TeamBeOS as well so not more than right that you take what is yours.
Good job =)
Well, at least you appear to have second position secured for a while 
I actually saw Serpentor take #1 from you the other day, but you had surpassed him again by morning 
You know, I checked on some of the machines at work and found that many of them were just sitting there, not crunching numbers so I stopped and restarted them and they are running fine again. I guess I need to check on them more often.
My good crunching may last throughout the summer but not much longer than that. I am finding out that SoB is affecting the performance of the machines to a point that they are so sluggish they are unusable. I have taken the client off about 6 machines over the past month because of this problem.
Remember, we are all in this together and I crunch for the team!!!
Viva TeamHaiku!!!
I am finding out that SoB is affecting the performance of the machines to a point that they are so sluggish they are unusable. I have taken the client off about 6 machines over the past month because of this problem.
You did change the priority of the client, right? 
It seems that both the Windows and BeOS clients don’t obey their configuration (for priority) so you have to set this manually. Not sure how the Linux client behaves…
The linux version runs with nice 19.
And it respects that setting. One can of course change it, but I can’t recommend that if you’re using a DE (especially true for Gnome).
You did change the priority of the client, right? :) It seems that both the Windows and BeOS clients don't obey their configuration (for priority) so you have to set this manually. Not sure how the Linux client behaves...
The windows (and BeOS?) client tries to intelligently set it’s priority internally - as far as the OS is concerned, it’s running at normal priority, but the client is monitoring CPU usage and yielding often.
If you want to MAKE the client run at TRUE IDLE priority in windows using sobsvc.exe - just run:
sobsvc -x
I don’t run any of my machines in this configuration, rather - whenever I need the extra processing power (for a compile, or a large zip file) - i just temporarily stop the service using the system tray icon.
I will try the -x parameter and see if that helps. Thanks for the info!