what's means of "stratum from pool 0 requested work restart"?

[supwang]

Hi, all:

When I mining with p2pool+cgminer, always show "stratum from pool 0 requested work restart". what does it means?
Thank you.

[1714129490]

1714129490

[1714129490]

1714129490

[1714129490]

1714129490

[1714129490]

1714129490

[1714129490]

1714129490

[evilpete]

The short version is that the work to produce the "next" block depends on the previous block.  The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful.  This is important because it encourages a "found" block to be used and distributed quickly.

You should see this message each time the bitcoin network as a whole finds a new block.

[supwang]

The short version is that the work to produce the "next" block depends on the previous block.  The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful.  This is important because it encourages a "found" block to be used and distributed quickly.

You should see this message each time the bitcoin network as a whole finds a new block.

Thank you.
Does it has any influence for the efficiency of mining? I found seems the increase speed of "accepted" reduced when this phrase appear over and over. (Is the psychological effect to me?)

[mitty]

The short version is that the work to produce the "next" block depends on the previous block.  The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful.  This is important because it encourages a "found" block to be used and distributed quickly.

You should see this message each time the bitcoin network as a whole finds a new block.

Thank you.
Does it has any influence for the efficiency of mining? I found seems the increase speed of "accepted" reduced when this phrase appear over and over. (Is the psychological effect to me?)

It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work.  There's nothing you can really do about it though, other than switch to a conventional pool but that might not really make a huge difference in your hashrate so I think you're fine. (it should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds.  That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.)

[supwang]

It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work.  There's nothing you can really do about it though, other than switch to a conventional pool but that might not really make a huge difference in your hashrate so I think you're fine. (it should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds.  That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.)

Thank you for your explain. Does it mean if I use "--fix-protocol" has no use for the hashrate?
Sorry for my poor english, you said that "That's why you can't use p2pool with devices that take a long time to start new work like BFL singles". Does it mean that I can not use p2pool+cgminer to mining 7*24?

[mitty]

Fix protocol simply prevents CGminer/bfgminer from attempting to auto-switch any getwork pools to stratum/gbt. I think you would would only use this in special cases where you only want to use getwork. If anything, using fix protocol could decrease your hash rate since getwork is less efficient than stratum or gbt.

And the issue I described with p2pool only applies to BFL single FPGAs, not GPUs, so you should be fine.
(Yes, you can use it 24/7 with GPUs and it will work fine)

[supwang]

Fix protocol simply prevents CGminer/bfgminer from attempting to auto-switch any getwork pools to stratum/gbt. I think you would would only use this in special cases where you only want to use getwork. If anything, using fix protocol could decrease your hash rate since getwork is less efficient than stratum or gbt.

And the issue I described with p2pool only applies to BFL single FPGAs, not GPUs, so you should be fine.
(Yes, you can use it 24/7 with GPUs and it will work fine)

Thank you. I'm using HD7970s*2 for mine now. Hope everything will be fine,hehe.

[n00bl0r14n]

Greetings! This might seem dumb.

I run cgminer 3.12.3 with BF1 with the setup: "cgminer -o http://mint.bitminter.com:8332 -u username_worker -p random".
Does the mining just simpy stop or do I have to press the reset button (wich I just did) on the BitFury or will it continue automaticly after x time?

If so, is there any automated command for that?

[Foysal]

The short version is that the work to produce the "next" block depends on the previous block.  The moment a new block is found, any in-progress searching is aborted because it won't produce anything useful.  This is important because it encourages a "found" block to be used and distributed quickly.

You should see this message each time the bitcoin network as a whole finds a new block.

Thank you.
Does it has any influence for the efficiency of mining? I found seems the increase speed of "accepted" reduced when this phrase appear over and over. (Is the psychological effect to me?)

It might very briefly decrease your mining hashrate because of the time required to fetch new work from the pool/start working on the new work.  There's nothing you can really do about it though, other than switch to a conventional pool but that might not really make a huge difference in your hashrate so I think you're fine. (it should be noted that p2pool has 10-second blocks so you'll see this message about once every 10 seconds.  That's why you can't use p2pool with devices that take a long time to start new work like BFL singles.)

Quick question.

I've just moved to a P2Pool for the first time (this morning) I have a mixed rig of block errupters and ant miner U1s - would they work ok with a P2Pool? Or do you think I would experience HW issues?

~Foyz