1
MemoryCoin / Re: XPool - How to continue & fix problems...
« on: December 25, 2013, 11:03:05 pm »
just a heads up, another pool was launched: http://mmcpool.com/
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hell yeah! Primeminer shows 2-3 primes/s. WTF? Wallet told me, I was mining (for test) in speed ~3.17 h/m.are you in the right thread here? Title is: mmc.xpool.xram.co - First Memorycoin Pool
for choosing, I would create a new thread saying pool operators wanted to run an instance of the pool, and I would be looking for people who can show that they have some understanding of how to code. It would be selective, for sure.i meant how you be sure that they wouldn't just steal your code and make their own independent pool...
yeah, it would be inefficient, but this is only meant as a temporary solution, until you get things under control... and also, if you mention the pool operators working with you, it might be exactly the collaboration you were looking for... i don't know how you would choose them thoughi see you limited the number of workers... how about creating another pool with this limit? maybe on another port or something
yeah, I really should have multiple instances of the pool. That would be cool.
Unforunately, I would have to do some changes to the JSON-RPC, and make the web interface unified, but its a good idea. I could also license pool operators... if that makes sense... to run a instance of the pool publicly for mining, and the web interface could connect and retrieve stats and unify it as XPool. The other pool operators could work with me to improve the code and solve problems.
That still seems inefficient though...
pool has been restored finally.it shows 807 workers, u sure it's limited?
NEW: Client limit. Has been set to 800 for the time being. If you cant connect and the website works, that is why. First come first serve.
I did this because the pool handles that amount properly, but add much more, and problems occour.
Payouts should occour within 30 minutes... hopefully that happens
EDIT: Check out the website, now shows the number of clients, so you know when to connect.
dmesg -T | tail
[Wed Dec 25 20:17:24 2013] systemd-journald[101]: Failed to write entry (25 items, 211571354 bytes) despite vacuuming, ignoring: Argument list too long
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Deleted empty journal /var/log/journal/bb9d0a52a41243829ecd729b40ac0bce/user-1000@c4ef46c298b543f9ab9fbe27625479c4-0000000000000000-0000000000000000.journal (3735552 bytes).
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Vacuuming done, freed 3735552 bytes
[Wed Dec 25 20:19:02 2013] systemd-journald[101]: Failed to write entry (25 items, 237032090 bytes) despite vacuuming, ignoring: Argument list too long
... and that message is repeated many times.
is this normal? i mean the duplicates... what does the first number actually mean?
hash generated - 7502 / 1968 / 3640808312
hash generated - 10725 / 1968 / 3757984692
hash generated - 13317 / 1968 / 2492638785
hash generated - 12666 / 1968 / 2015562052
hash generated - 12666 / 1968 / 2015562052
hash generated - 14294 / 1968 / 3536542128
hash generated - 14294 / 1968 / 3536542128
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 13666 / 1968 / 1088440815
hash generated - 12510 / 1968 / 3560445581
I have never seen that before... do you hash quickly?
are you submitting double shares?
stats for 64 core and 64 threads
[STATS] 2013-12-25 19:23:21 | SHARES: 5 (100.0% | 5.4/h), VL: 5 (62.5%), RJ: 3 (37.5%), ST: 0 (0.0%)