p2pool - miner settings suggestions ?

[girafon]

hi,

have anyone here some miner settings suggestions suitable for p2pool, for a low hashrate miner, with 250 - 270 Mhashes/s ?

i currently see longpoll work restart requests every second or so, so with current p2pool network (400Gh/s ~800 share diff), that means my miner app have 1 or 2 seconds to find a valid share against 800 difficulty ?

using cgminer, i currently use those:

Code:

"gpu-threads" : "1",

"expiry" : "10",
"scan-time" : "9",
"queue" : "0",

So ... it's heavily based on luck (i saw 0 seconds delay between longpoll requests....)

Any comment anyone ?
I'd really like to be able to use p2pool, although .. it looks like it is not for low-hashrate miners anymore...

cgminer 2.9.4
p2pool 9.0

[rav3n_pl]

Longpool in p2pool is every 10 seconds (average).
I`m mining at avg 150MH/s and there are times that I not get any share over 24hrs and sometimes I get 5 of them. This is only luck
Your miner settings are ok, higher queue leads to more DOAs and more threads in that MH/s power is just useless.
Sometimes longpools can hit every second or so, but it is 30s sometimes too. Avg form last few is always 10s - this way p2pool share chain is regulated (shares are too frequent -> share diff goin up).

[girafon]

Thanks for your answer,

Sometimes longpolls can hit every second or so, but it is 30s sometimes too. Avg form last few is always 10s - this way p2pool share chain is regulated (shares are too frequent -> share diff goin up).

Yep, i saw that 20 - 30 sec interval between longpolls too, i finally increased my scan time and expiry to fully rely on longpoll mechanism, i'll wait and see ...

I guess the reason for all those 0 - 1 second intervals between longpolls are somehow due to p2pool popularity increase / many people giving it a try, let's hope it will stabilize somehow, so web have at least a few seconds between longpolls

[rav3n_pl]

I guess the reason for all those 0 - 1 second intervals between longpolls are somehow due to p2pool popularity increase / many people giving it a try, let's hope it will stabilize somehow, so web have at least a few seconds between longpolls

Nope. This is only function of share diff, pool rate and luck - more share diff shares posted in row to chain. Maybe you see moment when some 10GH or more user join and put few shares on lower diff b4 pool catch this and increase share diff to keep avg 10s longpool
Scan time 60 is good enough, I never see longer longpool interval.

[cabin]

I had never set the queue size to 0.. but probably makes sense. I also read somewhere reducing the intensity by one (ie to around 7 or is a good idea so that there isn't too much of a delay in passing the new work to the GPU.