|
I get so little sleep since I discovered bitcoins that my coworkers say I look like a zombie every day.
|
|
|
|
|
Jine, you are spot on in your OP. We are patched for a large number of connections and today should be a good test for us.
|
|
|
|
|
Testing bitcoind v0.3.24 + Joel Katz v0.98 4diff on our pool. Going very well so far.
|
|
|
|
Just got done doing some major performance upgrades to the software on the server. We were only down for about 15mins (phew!). - do-release-upgrade to Ubuntu Natty Narwhal
- increased ext4 commit time
- custom compiled bitcoind v0.3.24 + pool patches by Joel Katz
The release upgrade (+kernel) and commit time increase was to fix a kernel bug that was causing constant writes to the storage. The custom complied bitcoind is for performance increases and provisioning for major scaling. I will be monitoring the server for the next few hours. Update: Went a little more aggressive on the ext4 tuning and it helped a ton. Not so much immediate performance, more for future scalability. |
|
|
|
Well we were VERY lucky on our first two blocks, so this kind of makes up for it. We've just barely hit the average.
That's the Truth Truth!  |
|
|
|
|
I think he stopped breathing and died because we didn't give him a reason to keep breathing. First bitcoin suicide?
|
|
|
|
As far as a pull request, it's unlikely it will be mainstreamed due to some of the features/changes are not good for clients. Though maybe I misunderstood that part? I'd be happy to see it in the mainstream code.
I agree with you. This is a pool oriented fork and Jay Garzik will probably take a couple seconds to look at the code and then close the pull request. |
|
|
|
|
Is everything stable, yet? Time to freeze the code? Release Candidate #1? No new features planned? I really want to run this code on my pool and it sounds like you have hit a milestone.
|
|
|
|
|
Long round is making this monkey very angry. We've already lost some hashrate to pool hoppers, grrr.
Reminder: You can't win the bounty if you pool hop! You have to submit the winning share that finds the block.
|
|
|
|
|
I think they are warning everyone who uses Dwolla. I don't think they are notifying people based on who they have sent/received from.
Edit: I'm stupid, "one of the merchants whom you have done business with"
|
|
|
|
|
I think I jumped the gun. I believe I am having a real hardware problem. It's only on one card, the hotter one of the group, and it's overclocked and over-volted to all hell. I think what happened is that these errors were hidden from the console until this new kernel update! If that's the case, kudos for making the errors work! haha.
|
|
|
|
They might figure that some people use the same password for both Dwolla and Mt Gox. It's probably just a precaution.
Aren't they a little behind on this news though?? |
|
|
|
|
I got this e-mail too. Dwolla does business with many other types of industries, not just bitcoin. So, did a bitcoin related site get hacked or did some other obscure website get hacked?
|
|
|
|
|
Yes I copied over the init file, because without it it won't even run. Windows 7 64-bit, Catalyst 11.5, Stream 2.4. Haven't had this message pop up with any other version of phatk kernel, nor any other kernel for that matter.
|
|
|
|
|
Thanks for the donation Xenland!
|
|
|
|
New version 2011-07-17 getting a lot of: 2011-07-18 01:24:09: Listener for "bitcoinmonkey": [18/07/2011 01:24:09] Kernel error: Unusual behavior from OpenCL. Hardware problem? |
|
|
|
I want to track this thread, so I'm replying to it  |
|
|
|
We now got 6 last balanced pushpoold/bitcoind nodes.  Now it's time for some coding on the new system, I've had to postpone it until now due to the issues, rejected shares and stability issues. Everything seems to work better now, that's really, really good  I'll keep you guys updated. That's a pretty nice little Xen cluster for a bitcoin pool You should get a NetApp now, hehe. |
|
|
|
|
Our pool uses pushpoold with a custom script for Long Polling which works better than blkmond. I'm not sure what information you are trying to gather, but pushpoold is no longer the problem as I first suspected. JoelKatz has patched the heck out of bitcoind for pool operators to bring the bottleneck from ~300GH/s to ~1000GH/s and other improvements.
|
|
|
|
|
zOMG the new Trixx works!! I've been waiting for this day for weeks! FWIW I had to disable the Synchronize cards in Multi-GPU config and use the drop-down menu to overvolt/overlock the cards independently.
|
|
|
|
|
Show Posts
