Quote from: Red Emerald on December 21, 2012, 04:05:53 AM

Quote from: K1773R on December 21, 2012, 02:51:57 AM

Quote from: Red Emerald on December 21, 2012, 02:49:45 AM

Quote from: K1773R on December 20, 2012, 01:32:30 PM

Quote from: svirus on December 19, 2012, 10:54:19 AM

Quote from: CosicMiner on October 29, 2012, 02:23:43 PM

My getwork latency is 0.211s mean. Had one spike up to 0.8s
I dont know if its good or bad. Whats your latency?
Also how can i optimize?

Use bitcoind from git.
Put bitcoind on SSD disk if you have.
Or use some RAID array.

On my RAID1 (mirror) with 2 disk 10k RPM i have under 0.1 latancy (now is 0.0539s mean)

even better, use it over ext4 for extreme caching speed Tongue

also renicing it to -10 gives ALOT of latency reduce

I hadn't thought about using nice or ext4. I'll have to try that.

I think ionice might help even more.

ionice is unecessary with ext4.

Really? Why is that? A quick google search didn't turn up anything.

I'm on ext3, so I'll play with ionice anyway

ext3 has some seconds until a flush of queue is forced, ext4 up to 120 seconds, therefore u can read/write alot (my ext4 got 4GB buffer Tongue

depends on system/kernel settings) and therefore u can easely write/read stuff without the need for flushing it instantly, therefore new miners will get the work and some seconds later it gets flushed to disk Wink

ionice is good if there is continues rw going on @ the HD, but if you do all these operations in cache anyway it dosnt matter. you should ionice it to -c 3 (idle) otherwise the whole system may hang while its being flushed (then even p2pool cant write to its sharechain). sry for all the typos, tired as hell, gtg sleep Tongue