Continuing thoughts into what Avalon's display
https://bitcointalksearch.org/topic/m.17968629 and followup
https://bitcointalksearch.org/topic/m.18027671 as massively spikey 5-sec hash rates, wonder it is from how/when the 1 controller is talking to the 3x 721's chained off of the 1 USB/I2C adapter coupled with how Canaan's (legal) fork of CGminer reads that? Looking at what Canaan's GUI displays they must be smoothing out a lot of samples...
Perhaps for several sec or more there is nothing to report to AM followed by a massive data burst as the miners in unison report findings/request more work? I can easily see that the light on the adapter only flashes with a burst of activity for a couple sec maybe 5x a minute.
Thanks for all info on the Avalon hashrate you have provided. Based on your previous posts, it looks like the 5s hashrate is reported with a large variation. Awesome Miner is currently not smoothing any values - everything is displayed exactly as reported by the miner API's.
It would probably be possible to add some smoothing to the graphs in Awesome Miner, but the question is really if you want to see a pretty graph or a graph showing what's actually reported.
Not so much a pretty graph, but one that displays large variations better. Say a log-scale display option with 2 or 3 steps. I agree it is good to know/see how the Avalons are really reporting.
Why as many as 3 steps eg. 0-10, 10-100, 100-1000THs? 1 Avalon RasPi controller can run up to 20 miners. With Avalon 741's that is 150THs sustained average reported as 1 miner. God knows what the reported peaks would be....
That way AW's auto scaling doesn't result in the lower hash rate miners (s7's & 12-14THs s9's!) being swamped out. Speaking of which, today I added a741 to the chain of 3x 721's. Sustained hashrate reported by Kano is >28THs, on par with Canaan's GUI reports. However um, spikes over 100THs happen several times an hour so the s7's, R4, and yes even s9's are down in the mud...
A new bit about the Avalons/Controller: When miners are connected in a string off of 1 USB/I2C adapter, Canaan's GUI gives info about each miner in the string. AW reports them as 1 monster ASIC.
However, if I use 2 of the USB/I2C adapters and still just the 1 controller, then Awesome reports the new adapter/miners chain as a 2nd ASIC in the miner (controller). Of course as desired Awesome does still report just one miner and total specs on its output.
Point is, if I want to see how each individual miner is running then I can only run 4 physical miners per 4-port RasPi. Rather defeats the point of being able to chain 5 physical miners from each of the 4 USB ports giving 20 miners per controller.