AVALON ASIC has delivered first RIG (68GH/s Confirmed) 2nd out proof

[creativex]

I wouldn't be at all surprised if they had some sort of production problem and are milking the CNY/customs excuses to give them time to fix it.

[iCEBREAKER]

I suspected that as well.  Especially since the extremely high profile first unit, hand delivered for review, is constantly freezing and requiring reboots.

[Bicknellski]

Runs 24 hrs straight no reboot or freezing for the most part this was an issue with the type of pool settings. See  https://bitcointalk.org/index.php?topic=140539.160


   

Re: Avalon ASIC users thread
February 05, 2013, 08:35:10
  #159

More good news.  Machine uptime and cgminer uptime are both now 24 hours.  Pool was BTC Guild, and stratum seems to most commonly use a share difficulty of 32.00000.

Now going to play with p2pool some more, with higher difficulty rates.

It sounds like a theory of a memleak is certainly plausible, at least.

   
Re: Avalon ASIC users thread
February 06, 2013, 03:27:36
  #170

Survived 18 hours so far on p2pool without a restart, either machine or cgminer.

Mining at difficulty 16.0, with stratum, to local p2pool/bitcoind.




Re: Avalon ASIC users thread
February 06, 2013, 04:42:07
  #171

Miner "freeze" just past hour 20, mining p2pool:  openwrt and cgminer status are accessible, but no work is being retrieved from / sent to p2pool.

Manually restarted.

[MrTeal]

I wouldn't be at all surprised if they had some sort of production problem and are milking the CNY/customs excuses to give them time to fix it.

That, or they decided that rather than finalize all the wafers they would just finish metal on one and see how it turned out before committing all their wafers. Now that they know there's no issue, they have to get everything finished for the rest of the wafers.

Obviously that's just speculation and Avalon has (rather intentionally IMO) cultivated the idea that they won't give updates and products will just show up, so it's hard to say much at this point.

[Turbor]

Runs 24 hrs straight no reboot or freezing for the most part this was an issue with the type of pool settings. See  https://bitcointalk.org/index.php?topic=140539.160

24 hrs ? nothing to be proud of imo.

[superfastkyle]

How long until Avalon is a scam again. A week or two without any more asic being delivered?

[Syke]

Runs 24 hrs straight no reboot or freezing for the most part this was an issue with the type of pool settings. See  https://bitcointalk.org/index.php?topic=140539.160

24 hrs ? nothing to be proud of imo.

That device has already paid for itself. Now he's making over $200 profit every single day. I'd be quite happy with that situation.

[creativex]

Runs 24 hrs straight no reboot or freezing for the most part this was an issue with the type of pool settings. See  https://bitcointalk.org/index.php?topic=140539.160

24 hrs ? nothing to be proud of imo.

That device has already paid for itself. Now he's making over $200 profit every single day. I'd be quite happy with that situation.

Agreed. What Avalon has accomplished in such a short time frame is amazing.

[jgarzik]

That device has already paid for itself.

Not yet.  Maybe another 1-2 days.

Now he's making over $200 profit every single day.

Not true... I wish.

[SgtSpike]

That device has already paid for itself.

Not yet.  Maybe another 1-2 days.

Now he's making over $200 profit every single day.

Not true... I wish.

http://www.alloscomp.com/bitcoin/calculator says 68 GH/s is just over 10 BTC a day...

[jgarzik]

http://www.alloscomp.com/bitcoin/calculator says 68 GH/s is just over 10 BTC a day...

Sure, that's the predicted average.  Machine/miner reliability, bad luck, the pool's cut, costs related to pool hopping and other factors definitely impact income.  p2pool's income was something like 50% below predictions.

[mrb]

I would mine solo if I were you. A block solved every 2.5 days on average.

[SgtSpike]

http://www.alloscomp.com/bitcoin/calculator says 68 GH/s is just over 10 BTC a day...

Sure, that's the predicted average.  Machine/miner reliability, bad luck, the pool's cut, costs related to pool hopping and other factors definitely impact income.  p2pool's income was something like 50% below predictions.

Wow, quite the toll on expected earnings!

[jgarzik]

I would mine solo if I were you. A block solved every 2.5 days on average.

Already tried and failed mining solo with: bitcoind, p2pool, eloipool.  And I know enough to know that my own pushpool, unmodified, cannot keep up either

Need to hack pushpool or use another proxy server that can keep up.

[SgtSpike]

I would mine solo if I were you. A block solved every 2.5 days on average.

Already tried and failed mining solo with: bitcoind, p2pool, eloipool.  And I know enough to know that my own pushpool, unmodified, cannot keep up either

Need to hack pushpool or use another proxy server that can keep up.

Have you tried BitMinter?

[MooC Tals]

Use a ridiculous amount of threads

[mtminer]

I would mine solo if I were you. A block solved every 2.5 days on average.

Already tried and failed mining solo with: bitcoind, p2pool, eloipool.  And I know enough to know that my own pushpool, unmodified, cannot keep up either

Need to hack pushpool or use another proxy server that can keep up.

I had good luck with http://poolserverj.org/ I put mysql on a SSD and it kept up with 30 gighash on a old core 2 1% cpu usage. Was fun to query the db to get the current speed.

SELECT (COUNT(id) * 4294967296)/3600/1000000 as mhash_60,count(id) as total_shares FROM shares WHERE shares.time >= DATE_SUB( NOW(), interval 60 minute) and our_result = true;

[mrb]

Already tried and failed mining solo with: bitcoind, p2pool, eloipool.  And I know enough to know that my own pushpool, unmodified, cannot keep up either

Need to hack pushpool or use another proxy server that can keep up.

Set up eloipool with the difficulty set to some high value (eg. 64 with ShareTarget = 0x0000000003ffffffffffffffffffffffffffffffffffffffffffffffffffffff). Mine with getwork, not getblocktemplate. And make sure roll-n-time is functional. That setup should be able to handle hundreds of Ghash/s easily. That's what I use for my FPGA farm.

IIRC your pushpool and p2pool both hard-code the diff to 1. Isn't it why they can't keep up with the many getwork calls?

[jgarzik]

Set up eloipool with the difficulty set to some high value (eg. 64 with ShareTarget = 0x0000000003ffffffffffffffffffffffffffffffffffffffffffffffffffffff). Mine with getwork, not getblocktemplate.

Dynamic targetting was used, which should in theory achieve same... maybe high+static is better.

And make sure roll-n-time is functional. That setup should be able to handle hundreds of Ghash/s easily. That's what I use for my FPGA farm.

IIRC your pushpool and p2pool both hard-code the diff to 1. Isn't it why they can't keep up with the many getwork calls?

Multiple answers...

pushpool has several known inefficiencies... besides being single-threaded for database + network + rpc, it simply proxies every client getwork to bitcoind, with some rewriting.  bitcoind cannot keep up with that, once the miner load (historically difficulty 1.0) reaches a certain point, the whole system cannot keep up.

Pool ops either solve this by scaling up the number of bitcoind processes (machines), or run pool server software that supports some amount of internal work generation, easing bitcoind's load.

[mrb]

Set up eloipool with the difficulty set to some high value (eg. 64 with ShareTarget = 0x0000000003ffffffffffffffffffffffffffffffffffffffffffffffffffffff). Mine with getwork, not getblocktemplate.

Dynamic targetting was used, which should in theory achieve same... maybe high+static is better.

Yes, maybe. I have never tested dynamic targeting.