G@H Linux vs Windows

[rocketmanx]

Anyone have G@H running on Linux and windows boxes?
I'm messing around with Linux again (at least until I get tired of the antiquated look and feel again) and was wondering whether the Linux client was slower/faster than the windows client. The machines dual boot/dual proc and I don't want to waste a week of production checking the speed differences as I've got to beat Guru to 100k

[Guyver]

Aye - That I do.

Running G@H 0.99 on RedHat 7.2, MP kernel, Dual PIII-933 @ 1008Mhz, 384MB SDRAM PC133 (you do the math)

Running 4 sessions of G@H at nice level 0 - been up since I did the OS upgrade almost 2 months ago.

My Windows XP Dual Proc @ 1000 Ghz can only sustain 3 sessions and have decent output.

I even tried running 2 sessions each on my Single CPU XP and 2K boxes without much success - too slow afterwards.

Guyver

[rocketmanx]

Thanks Guyver!
How do you run multiple clients and set affinity and priority?
I haven't figured out how to run multiple instances and set priority in Linux yet, haven't had enough patience and I'm not exactly a "manual reader", I like to flail my way through it's much more fun/frustrating

Thanks
Pete

BTW- You watch college ball? One of our local High school stars (notorious now for starting the controversy that got Bobby Knight fired) is playing for Iowa now.

[Guyver]

I will post a copy of my startup script for G@H on Linux.

I created several subdirectories under my home dir.

ghclient1, ghclient2, ghclient3, ghclient4.

I call it GenomeStart.sh

[ ${#} -eq 0 -o "${1}" = "1" ] && {
   cd ${HOME}/ghclient1
   2>&1 1>/dev/null nohup $( pwd )/ghclient.x &
}
[ ${#} -eq 0 -o "${1}" = "2" ] && {
   cd ${HOME}/ghclient2
   2>&1 1>/dev/null nohup $( pwd )/ghclient.x &
}
[ ${#} -eq 0 -o "${1}" = "3" ] && {
   cd ${HOME}/ghclient3
   2>&1 1>/dev/null nohup $( pwd )/ghclient.x &
}
[ ${#} -eq 0 -o "${1}" = "4" ] && {
   cd ${HOME}/ghclient4
   2>&1 1>/dev/null nohup $( pwd )/ghclient.x &
}
sleep 30
renice 0 $( pgrep ghclient.x )

Essentialy running the script with no parameters will start all 4 sessions. Or, in case one has failed, you can add 1 parameter for the number of the session you wish to restart. I use the fully qualified path name for the client so that a ps -ef will show which sessions are still running (given the path name shown).
It then executes a renice 0 on the output of the pgrep ghclient.x command.

It could easily be modified to allow multiple client starts, and I can probably right a monitoring daemon that would watchdog the procs and if one died, would restart the client, if it died twice, would run a clear, and then restart.

Guyver


PS - Sorry, I am not a sports fan. I think the education system as a whole would be far better off without sports entirely (aside from the normal phys-ed of course). That would put the emphasis back on education - not on physical performance.

(Stepping back in case this one blows up in my face - donning asbestos suit, with shuttle-tile armor)

[rocketmanx]

Thanks Guyver
Scripts and the command line are not something I have taken up yet. DOS was the reason why I hated computers when I was first exposed to them back in the day of Doom- seemed to me that computers were supposed to make things more of a no-brainer sorta' like calculators do with math. I've never seen a calculator that required learning a 1000 page manual of cammands
Agree on the sports (I was a book-worm/science/art geek when I was in school) just curious as my wife works with this guys mom and I am always hearing about wht's going on with Luke in Heaven
Thanks Guyver
Pete

[lurqa_MU]

Why re-nice the clients?

Originally posted by Guyver

.......
sleep 30
renice 0 $( pgrep ghclient.x )
...........

Why would you want to renice the processes to 0?

Do you have some other less important processes running on the machine, or is it to make the 4 processes share the 2 CPU's more efficiently?

Regards,
lurqa

[Guyver]

I essentialy up'd the priority which starts at a base 20 (lower is higher priority). This allows system processes (usually with a negative nice number) to run ahead of ghclient, but essentially everything else runs at the same priority as ghclient.x.

Guyver