[ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool

[flashoftheblades]

For me it seems that the reject rate it going up for miners which do not have that my cores.

I am currently using 2x 32 core AWS spot instances for testing throughput, an 8 core i7
and a couple of 3 core virtual machines.

The reject rate for the 32 core monsters is below 1%
Reject rate for the 8 core is below 2%

And the reject rate for the 3 core things is at about 15% !!!
(I have 11 of those, and ALL of them have high reject rates)

I think I can see some pattern in this...

Unfortunately I don't know enough of the underlying work distribution software,
but maybe I am not the only one experiencing this situation and it would be
great if there might be some fine-tuning possible?

Who has the same experience?

I'm having the same observation mate. More cores - less rejections.

I would be more interested in the number of rejections vs the percentage. Presumably, a larger number of cores can process a larger number of shares, so if it's a fixed amount of rejects no matter the core number, it would appear to be a smaller percentage with more cores.

[xolokram]

if this is true it can be a very helpful information actually

@btc2084:
as you see the rejects come in blockwise (ends on "work received"), there's a bug somewhere (in the miner i ---guess---)
this is a known issues, there's a dirty workaround in the latest github (not helpful for windows user i know)

@recci:
protoshares is 1 year ahead of it's schedule... just saying 

- xolokram

ps. sorry, i dont have much time today for PMs/thread/community/tech support

[sony87]

For me it seems that the reject rate it going up for miners which do not have that my cores.

I am currently using 2x 32 core AWS spot instances for testing throughput, an 8 core i7
and a couple of 3 core virtual machines.

The reject rate for the 32 core monsters is below 1%
Reject rate for the 8 core is below 2%

And the reject rate for the 3 core things is at about 15% !!!
(I have 11 of those, and ALL of them have high reject rates)

I think I can see some pattern in this...

Unfortunately I don't know enough of the underlying work distribution software,
but maybe I am not the only one experiencing this situation and it would be
great if there might be some fine-tuning possible?

Who has the same experience?

I'm having the same observation mate. More cores - less rejections.

[jabbaah]

For me it seems that the reject rate it going up for miners which do not have that my cores.

I am currently using 2x 32 core AWS spot instances for testing throughput, an 8 core i7
and a couple of 3 core virtual machines.

The reject rate for the 32 core monsters is below 1%
Reject rate for the 8 core is below 2%

And the reject rate for the 3 core things is at about 15% !!!
(I have 11 of those, and ALL of them have high reject rates)

I think I can see some pattern in this...

Unfortunately I don't know enough of the underlying work distribution software,
but maybe I am not the only one experiencing this situation and it would be
great if there might be some fine-tuning possible?

Who has the same experience?

[devilfish]

Love how people come in here expecting easy money. Get a job if your that desperate for money, don't put your hopes into mining a digital currency.

Have a job mate! and don’t expect easy money. Just pointing out that this is probably not profitable for the average user to mine.

Love how people make over blown reactions to comments

So why come and tell us, we already know this, you aren't adding anything.

[Troglodactyl]

Clone from here and it will failover from beeeeer to rpool.

https://github.com/Troglodactyl/pts.git

Sounds good. Did you change anything else besides the auto failover?

I just added the additional pool to a list, and have it waiting for 3 seconds for work when it tries to connect.  If the pool doesn't give it work it disconnects and tries connecting to the next pool.  Kind of ugly with the hard coded pool list, but it was a quick hack to get my miners back up and hopefully keep them up.

[kargul]

I'm totally confused about all the "collision found" and "submitted share --> REJECTED" messages.

Do the messages below mean I'm not successfully mining?  Should I just go back to XPM?

[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:40:51 | 109.8 c/m | 4.0 sh/m | VL: 52 (82.5%), RJ: 11 (17.5%), ST: 0 (0.0%)
[WORKER] collision found: 65298305 <-> 63144468 #1762 @ 1386074483 by 3
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:04 | 110.6 c/m | 4.0 sh/m | VL: 52 (81.2%), RJ: 12 (18.8%), ST: 0 (0.0%)
[WORKER] collision found: 36950812 <-> 30198943 #1770 @ 1386074509 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-03 06:41:12 | 110.8 c/m | 4.0 sh/m | VL: 53 (81.5%), RJ: 12 (18.5%), ST: 0 (0.0%)
[WORKER] collision found: 61666229 <-> 11175757 #1798 @ 1386074502 by 6
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:15 | 111.6 c/m | 4.1 sh/m | VL: 53 (80.3%), RJ: 13 (19.7%), ST: 0 (0.0%)
[WORKER] collision found: 53826084 <-> 31172614 #1800 @ 1386074503 by 7
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:18 | 111.3 c/m | 4.1 sh/m | VL: 53 (79.1%), RJ: 14 (20.9%), ST: 0 (0.0%)
[WORKER] collision found: 16964194 <-> 40092960 #1808 @ 1386074525 by 5
[WORKER] collision found: 43809248 <-> 41984804 #1810 @ 1386074526 by 6
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:23 | 111.5 c/m | 4.2 sh/m | VL: 53 (77.9%), RJ: 15 (22.1%), ST: 0 (0.0%)
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:23 | 111.5 c/m | 4.2 sh/m | VL: 53 (76.8%), RJ: 16 (23.2%), ST: 0 (0.0%)
[WORKER] collision found: 30667112 <-> 26709513 #1820 @ 1386074490 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-03 06:41:29 | 111.6 c/m | 4.3 sh/m | VL: 54 (77.1%), RJ: 16 (22.9%), ST: 0 (0.0%)

Everything is fine, wait for blocks Where do you mine?

[btc2084]

I'm totally confused about all the "collision found" and "submitted share --> REJECTED" messages.

Do the messages below mean I'm not successfully mining?  Should I just go back to XPM?

[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:40:51 | 109.8 c/m | 4.0 sh/m | VL: 52 (82.5%), RJ: 11 (17.5%), ST: 0 (0.0%)
[WORKER] collision found: 65298305 <-> 63144468 #1762 @ 1386074483 by 3
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:04 | 110.6 c/m | 4.0 sh/m | VL: 52 (81.2%), RJ: 12 (18.8%), ST: 0 (0.0%)
[WORKER] collision found: 36950812 <-> 30198943 #1770 @ 1386074509 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-03 06:41:12 | 110.8 c/m | 4.0 sh/m | VL: 53 (81.5%), RJ: 12 (18.5%), ST: 0 (0.0%)
[WORKER] collision found: 61666229 <-> 11175757 #1798 @ 1386074502 by 6
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:15 | 111.6 c/m | 4.1 sh/m | VL: 53 (80.3%), RJ: 13 (19.7%), ST: 0 (0.0%)
[WORKER] collision found: 53826084 <-> 31172614 #1800 @ 1386074503 by 7
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:18 | 111.3 c/m | 4.1 sh/m | VL: 53 (79.1%), RJ: 14 (20.9%), ST: 0 (0.0%)
[WORKER] collision found: 16964194 <-> 40092960 #1808 @ 1386074525 by 5
[WORKER] collision found: 43809248 <-> 41984804 #1810 @ 1386074526 by 6
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:23 | 111.5 c/m | 4.2 sh/m | VL: 53 (77.9%), RJ: 15 (22.1%), ST: 0 (0.0%)
[MASTER] submitted share -> REJECTED
[STATS] 2013-Dec-03 06:41:23 | 111.5 c/m | 4.2 sh/m | VL: 53 (76.8%), RJ: 16 (23.2%), ST: 0 (0.0%)
[WORKER] collision found: 30667112 <-> 26709513 #1820 @ 1386074490 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-03 06:41:29 | 111.6 c/m | 4.3 sh/m | VL: 54 (77.1%), RJ: 16 (22.9%), ST: 0 (0.0%)

hi,

it looks like the pool completely lost the connection to the protoshares network (necessary to create work for the miners)
starting to produce orphans and being unable to give up-to-date data i'm sorry about this inconvenience

i'm currently restarting/reconnecting everything and checking what caused all this

- xolokram

ps. ok, everything has been restarted, i guess some of the remaining blocks are orphans too 
pps. looks like one of the more important nodes i use had a broken blockchain (using the vanilla protoshares client)
ppps. of course this happened while i was sleeping...

[recci]

Love how people come in here expecting easy money. Get a job if your that desperate for money, don't put your hopes into mining a digital currency.

Have a job mate! and don’t expect easy money. Just pointing out that this is probably not profitable for the average user to mine.

Love how people make over blown reactions to comments

[sony87]

Hello Xolo, lost connection to the protoshare network has caused the orphaned blocks and that no more block generation happen every hour like before ? I just put 30cores to mine and got nothing from last night

[btc2084]

Dear Xolokram,

Is this a bug?  When my DSL modem was powered off and then on, ptsminer crashed. 

The last message I think I saw was that it would retry after 10-seconds but I think right after that the window closed and it generated a crash dump.

For people with spotty internet connectivity you might want to try unplugging the ethernet to see how the app responds.  It crashed on my Win 8.1 box.

Thanks for your continued bug fixing.

hi,

it looks like the pool completely lost the connection to the protoshares network (necessary to create work for the miners)
starting to produce orphans and being unable to give up-to-date data i'm sorry about this inconvenience

i'm currently restarting/reconnecting everything and checking what caused all this

- xolokram

ps. ok, everything has been restarted, i guess some of the remaining blocks are orphans too 
pps. looks like one of the more important nodes i use had a broken blockchain (using the vanilla protoshares client)
ppps. of course this happened while i was sleeping...

[devilfish]

Love how people come in here expecting easy money. Get a job if your that desperate for money, don't put your hopes into mining a digital currency.

[BitThink]

Oops, lost whole day's mining.

@recci
Are you using optimized mining program? Your mining income seems one order of magnitude less than the normal value to me.

[recci]

This coin is incredibly hard to mine, I have been mining on an off for 4 or 5 days on 2 intel core i5's with 4 threads each and I still only have 0.04345 PTS. I thought is was meant to be mine-able for anybody, at this rate its not going to be profitable at all! Especially with the sky high cost of electricity in the uk....waste if time imo

[xolokram]

hi,

it looks like the pool completely lost the connection to the protoshares network (necessary to create work for the miners)
starting to produce orphans and being unable to give up-to-date data i'm sorry about this inconvenience

i'm currently restarting/reconnecting everything and checking what caused all this

- xolokram

ps. ok, everything has been restarted, i guess some of the remaining blocks are orphans too 
pps. looks like one of the more important nodes i use had a broken blockchain (using the vanilla protoshares client)
ppps. of course this happened while i was sleeping...