Personal computing discussed
Moderators: renee, farmpuma, just brew it!
cass wrote:switched the 650 duron and 1000 athlons around, put the 1000 on the k7t MB so it would OC with multiplier, and put the 650 duron on the acorp board since the acorp won't change multiplier, but will change fsb. Currently the 650 is somewhere around 750, and the 1000 athlon is running 1200. Now I must turn my attentions to OC the axp1800 and axp 1600.
ran cvsup last night for server, did buildworld and build kernel with -O2 -funroll loops on compiler, I have ran install world, install kernel and merge master... just need to reboot.
oz_eod wrote:I've been Folding with LWD now for a while. I just can't bring myself to jump ship with the systems I have now but I'd be willing to start up a Frankenbot machine if it's okay with you. If it is I'll work on getting a MB to get a 1.3 Athlon online.
oz_eod wrote:I've been Folding with LWD now for a while. I just can't bring myself to jump ship with the systems I have now but I'd be willing to start up a Frankenbot machine if it's okay with you. If it is I'll work on getting a MB to get a 1.3 Athlon online.
52server# ./rpm -q glibc
glibc-2.2.4-33
cass wrote:I don't use good memory either. kingston value ram is top of the line for me. I must be living good too, because I have not had any memory compatibility problems.
I did get a P1308 on the TRFbot 650 duron honestly... must have been all that was available.
The 3100 semprons I have will OC like no tomorrow, but even cranking from 1.8 Ghz to 2.2 does not help as much as it should. Of course at advanced speeds it kicks some butt on gromacs.
evidently freeBSD and Your linux are running the same linux subsystem.
so far I have tried recompiling the world and kernel using -02 -funrollloops and -03 with no noticeable difference.
the new GCC is supposed to net an 11% increase in speed, but I have not figured out how to get it installed yet.
JBI, are you running polling on your network server, or are U using interrupts.? I am not sure if that question will make any sense to you, but if freeBSD, it is an option to force the kernel to check every so often for other interrupts needing servicing rather than just handing control over to the 1st interrupt and letting it have control (however scheduled) till finished. It is said polling is good for a heavy load to keep from starving processes (clients) in a heavy load net server environment.