by the way, alot of "miner is idle" the last minutes in eu server!
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 224. (Read 499702 times)
June 17, 2011, 03:55:43 PM
no, i meant one person alone cannot run a big pool with all those problems andd DDos
by the way, alot of "miner is idle" the last minutes in eu server!
by the way, alot of "miner is idle" the last minutes in eu server!
June 17, 2011, 03:34:51 PM
i hope you are not alone in all this!
one person pool is just impossible!
You aren't alone :pone person pool is just impossible!
I'm here mining with you
June 17, 2011, 03:32:40 PM
i hope you are not alone in all this!
one person pool is just impossible!
one person pool is just impossible!
June 17, 2011, 01:53:02 PM
I will look into that once I get everything stable and most of the features finished. I still have a giant list of features I plan on adding, it's sitting on my desk (the list) staring and me and mocking me.
Share it with us, so we can give you some little tips 
EDIT: Read my PM please
June 17, 2011, 01:52:19 PM
I will look into that once I get everything stable and most of the features finished. I still have a giant list of features I plan on adding, it's sitting on my desk (the list) staring at me and mocking me.
June 17, 2011, 01:40:08 PM
Excellent... I tried to code it as carefully as possible without being able to test it!
What about putting some giveaways for miners? Like for the top 10 miners..
That would increase the pool hashrate and many users will join!
June 17, 2011, 01:38:49 PM
Excellent... I tried to code it as carefully as possible without being able to test it!
June 17, 2011, 01:30:02 PM
If you want to force an alert, setup an alert for a failed worker for like 1 minute, then turn off that worker for a minute and it should try to SMS you. I'd set an email alert as well, so you know when it fires the alert.
Works!Miner alert -> Myworkername has failed! Last activity was (putdatehere)
June 17, 2011, 12:54:10 PM
If you want to force an alert, setup an alert for a failed worker for like 1 minute, then turn off that worker for a minute and it should try to SMS you. I'd set an email alert as well, so you know when it fires the alert.
June 17, 2011, 12:10:04 PM
Organofcorti: I am glad the speed is improving. I still have a major speed improvement push to the worker server process that I plan on today and if that doesn't completely solve the PACRIM issue, I have one more thing that I'm fairly certain will fix it, it just adds more complexity and cost to the non-US servers, so I've been avoiding it. Keep it simple and there's less to break!
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Going to test the SMS phone support when a block will get solved Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Could you check the thread I made in the official forum of the pool? Thank you!
June 17, 2011, 12:08:05 PM
Organofcorti: I am glad the speed is improving. I still have a major speed improvement push to the worker server process that I plan on today and if that doesn't completely solve the PACRIM issue, I have one more thing that I'm fairly certain will fix it, it just adds more complexity and cost to the non-US servers, so I've been avoiding it. Keep it simple and there's less to break!
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
June 17, 2011, 08:50:48 AM
Hey Inaba, a bit better on pacrim tonight (20:05 to 23:35 AEST)
gpu1: 3 and a half hours on pacrim, poclbm reporting ~ 376 Mhps: 875 shares (expected hashrate=298 Mhps)
gpu2: 3 and a half hours on other pool, poclbm reporting ~ 369 Mhps: 1009 shares (expected hashrate=344 Mhps)
That's about 15% better - whatever you're doing keep it up! Thanks so much for the work you're doing on it. As soon as you have the pacrim wrinkles ironed I'll be fulltime. Also looking foward to your implementation of the anti-pool hopping algo.
Cheers!
gpu1: 3 and a half hours on pacrim, poclbm reporting ~ 376 Mhps: 875 shares (expected hashrate=298 Mhps)
gpu2: 3 and a half hours on other pool, poclbm reporting ~ 369 Mhps: 1009 shares (expected hashrate=344 Mhps)
That's about 15% better - whatever you're doing keep it up! Thanks so much for the work you're doing on it. As soon as you have the pacrim wrinkles ironed I'll be fulltime. Also looking foward to your implementation of the anti-pool hopping algo.
Cheers!
June 17, 2011, 06:56:06 AM
Pointed my 186 MHash/s here!
Little question, will the SMS notifications arrive to my Italian phone? I inserted the prefix in the cellular number but I wanna be sure
Also, remove the share validation period and add IPV6 and this will be the best pool ever!
Little question, will the SMS notifications arrive to my Italian phone? I inserted the prefix in the cellular number but I wanna be sure
Also, remove the share validation period and add IPV6 and this will be the best pool ever!
June 17, 2011, 04:20:39 AM
very nice site! 0% fee is wining 
June 17, 2011, 03:47:05 AM
Sorry about that! I was treating that as an integer instead of a float, so anything less than 1 was getting set to 0.
It's fixed now, though. You should be able to change it to a fraction of a btc, but no less than .02.
I apologize to the PACRIM people; I've been rewriting a huge chunk of the worker servers share and statistics code to speed things up dramatically and in the process I think I've identified what's been slowing down PACRIM. It's late here, though and I don't want to push the new code to the servers unless I can watch it for awhile in case it crashes. I plan on pushing it out tomorrow along with the original changes to speed things up... between the two it should make PACRIM just as fast as the US server hopefully.
I've already made some changes on the backend though and that might solve a good portion of the speed issues.
It's fixed now, though. You should be able to change it to a fraction of a btc, but no less than .02.
I apologize to the PACRIM people; I've been rewriting a huge chunk of the worker servers share and statistics code to speed things up dramatically and in the process I think I've identified what's been slowing down PACRIM. It's late here, though and I don't want to push the new code to the servers unless I can watch it for awhile in case it crashes. I plan on pushing it out tomorrow along with the original changes to speed things up... between the two it should make PACRIM just as fast as the US server hopefully.
I've already made some changes on the backend though and that might solve a good portion of the speed issues.
Thanks, it looks fixed now. This pool of yours has a lot of potential. 0% mandatory fee + LP + Automatic payout threshold = Greatness!
Hopefully your server comes back up soon enough, as I want to kick off my new card on it soon and see how it goes!
June 17, 2011, 03:37:47 AM
Can't connect to US, EU or ASIA addrs.
When I ping
Same, it seems that the pool servers are offline, since the GHash/s are lowering (from 22+ to 8 now) When I ping
Quote
ping pacrim.eclipsemc.com
PING pacrim.eclipsemc.com (46.51.255.204) 56(84) bytes of data.
it returns nothing.PING pacrim.eclipsemc.com (46.51.255.204) 56(84) bytes of data.
June 17, 2011, 03:35:45 AM
Can't connect to US, EU or ASIA addrs.
When I ping
When I ping
Quote
ping pacrim.eclipsemc.com
PING pacrim.eclipsemc.com (46.51.255.204) 56(84) bytes of data.
it returns nothing. PING pacrim.eclipsemc.com (46.51.255.204) 56(84) bytes of data.
June 17, 2011, 03:05:10 AM
I think I'll join when all the Coming soon features will be completed!
Nice GUI!
Nice GUI!
June 17, 2011, 02:03:42 AM
Sorry about that! I was treating that as an integer instead of a float, so anything less than 1 was getting set to 0.
It's fixed now, though. You should be able to change it to a fraction of a btc, but no less than .02.
I apologize to the PACRIM people; I've been rewriting a huge chunk of the worker servers share and statistics code to speed things up dramatically and in the process I think I've identified what's been slowing down PACRIM. It's late here, though and I don't want to push the new code to the servers unless I can watch it for awhile in case it crashes. I plan on pushing it out tomorrow along with the original changes to speed things up... between the two it should make PACRIM just as fast as the US server hopefully.
I've already made some changes on the backend though and that might solve a good portion of the speed issues.
It's fixed now, though. You should be able to change it to a fraction of a btc, but no less than .02.
I apologize to the PACRIM people; I've been rewriting a huge chunk of the worker servers share and statistics code to speed things up dramatically and in the process I think I've identified what's been slowing down PACRIM. It's late here, though and I don't want to push the new code to the servers unless I can watch it for awhile in case it crashes. I plan on pushing it out tomorrow along with the original changes to speed things up... between the two it should make PACRIM just as fast as the US server hopefully.
I've already made some changes on the backend though and that might solve a good portion of the speed issues.
June 17, 2011, 01:14:50 AM
I am seeing a bug when changing the automatic payout threshold. After I changed it to 0.10, it changed itself to 0, and now won't change at all.
Jump to: