Another RC5 config question and why it's doing this....

[NicColt]

This is what I have in my ini file

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=5000
randomprefix=252

I asked the setup to fetch 5000WU's it did it the first time but now when I asked it to fetch work it only tops it off to 500 Packets or around 3040WU's. Is this normal.

 

[ViRGE]

I belive that the client has a limit of around 3K WUs or so; though I haven't heard much about this lately.

 

[SuenoNL]

I think 500 packets is the maximum # of packets that your client can ask for... So basically your client said: "hey proxy, give me 500 packets, but stop after I got 5000 workunits."

The proxy gave you the 500 packets, but obviously didn't get to a total of 5000 workunits, probably because it didn't have enough of the biggest packets available...


With a little more work you can get a higer # of workunits though.. you need to retrieve a 2nd in-buffer and import it in the client manually..

a. close the client
b. open explorer and find your buff-in.rc5
c. rename the buff-in.rc5 to some other name, like niccolt.nr1 for example
d. restart the client
e. make it fetch another 500 packets (if not done automatically)
f. close the client
g. on the command line, type : dnetc -import niccolt.nr1
h. restart the client, et voila... 1000 packets there, containing several thousands of workunits

Of course, you can repeat step c-h a gazillion times and get a really huge inbuffer, but that's a helluvalot of work, if you need a huge buffer, you should install your own proxy.

 

[dkappos]

yes the clients do not fetch more than 500 packets. If you want for any reason to make a bigger buff-in you can rename your buffer file, then fetch new work units and import the one that you have renamed.

 

[dkappos]

I wasn't fast enough

 

[NicColt]

thanks guys for the info, at least it's normal then. I though something was wrong.