64 block packets

[LeBlatt]

It seems that Mika is handling mostly, if not only, 64 block packets (or 2^34) recently.
Thats a great opportunity to reduce
-memory used by the ppoxy on mika's box
-the size of logs, thus the time it takes to process stats every 15 mn
-the uplink time of fetching/flushing

So please everyone set your preferred packet size to 2^33 (or 32 block packets)
and your fetch threshold to a multiple of 32, or better yet, 64.

If you're concerned that your cruncher could be accidentaly stopped in the middle of a 32 block packet (which is quite a beast for slower machines) you should consider using checkpoints, they save work every 10 minutes. The only place where I wouldnt advice this is on a slow and unstable machine that cracks in memory only. But who uses that ? ; )

FYI, a Celery@850 swallows a 32 block packet in a little under 1 hour.

 

[JHutch]

Didn't I hear that DNet was thinking about moving to even larger packet sizes in future clients? So that the client could grab a 64 block packet as well (2^34)? That would help cut net traffic quite a bit.... Espcially for some of our borg-class crack-addicts!

JHutch

 

[jinsonxu]

Now, i've set my client to 2^33 but i sometimes get only 1 or 4 workunit in 1 packet.

Only about 60% of the time do i get 32 workunits in 1 packet. Usually takes about 20-30Minutes to finish it.

 

[RaySun2Be]

I've got mine all set to 33, will have to go back and check about the fetch # of blocks.

Heya LeBlatt, YGPM!