Pool and network electricity use, hashrate and miner count distribution 2nd July 2013

2nd July 2013

Last post

0. Introduction

There was a significant increase in ASICMiner's hashrate this week. Because of this, and also because I only have access to user hashrates for ~ 59% of the network, this week's estimate may be incorrect. I'm not sure I believe 7000 miners just left the network, for example. However, the network electricity use estimate will not be significantly affected by this.

The assumptions I've used to create this data are outlined here.

The raw user hashrate data is here. It's an Rdata file, and consists of a dataframe named "alluserHR.df " with 207079 rows and three columns - Date, Pool (this includes ASICMiner), and UserHR (the hashrate of pool account holders in Ghps). Let me know if you do something interesting with the data.

1. Network: Per Ghps band user count, summed hashrate, and summed electricity.

2. Pools: Per Ghps band user count, summed hashrate, and summed electricity.

Most pools are experiencing declines in the numbers of users in the < 5 Ghps band.

3. Efficiency, joules per Gh (eq. watts per Ghps)

This chart is not meant to be a value judgement on any pool; rather you can think of the efficiency as a guide to the proportion of different types of hashing tools. The higher the J/Gh, the less efficient the hashing entity is (pool, network or solominer), and the higher the proportion of CPUs and GPUs to ASICs.

Since there can be significant variance per week I'm using cubic splines, so curves may vary from week to week.

4. The Survey is done!

Thanks to all who participated! I'll publish the results as soon as I have time to clean them up, and I'll have a new survey out after that. Let me know if there are specific statistics you'd like me to present.

organofcorti.blogspot.com is a reader supported blog

BTC:  12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r

LTC:  LPXnETNoCBr16GduvyWRzFP83rZNeEgMuB

For notification of new posts, follow @oocBlog