[l008com]

I'm wondering about the Dnet client, and how well does it 'get out of the way' for other programs. I'm running a 225MHz OS X Server and I wanna run dnet on it to get a few extra blocks (it only take one to win), but I wanna make sure that it will COMPLETELY get out of the way for all my web and mail services when my sites are under heavy load, or just heavy spikes.

[mikkyo]

Originally posted by l008com:
I'm wondering about the Dnet client, and how well does it 'get out of the way' for other programs. I'm running a 225MHz OS X Server and I wanna run dnet on it to get a few extra blocks (it only take one to win), but I wanna make sure that it will COMPLETELY get out of the way for all my web and mail services when my sites are under heavy load, or just heavy spikes.

Try setting the priority to 0 (-priority 0) when you launch it, or in the ini file under [processor-usage] priority=0, or using the builtin ini config (./dnetc -config).

See how your server behaves with that.
If it isn't good enough, launch dnetc with nice of 20
/usr/bin/nice -n 20 ./dnetc

[l008com]

I always use priority 0 by default, im just wondering how the program itself behaves. Anyone have experience with it? I know on my G4, sometimes when doing long tasks like video encoding, dnet does not get out of the way, and shares the CPU 50-50. Not a good thing if my server gets a heavy load and i only get half of those 225 mhz.

[chris v]

Set it up to run, open Top, then launch a DOS attack on your own server from another machine. See if dnetc drops down to 0%.

With priority 0, I hardly ever notice it under os X, and when I'm running photoshop and working it hard, production can drop down to almost nil, making me think that it does get out of the way pretty much.

CV