The geobit project has been modularized.
Take a look at Rebecca https://github.com/RCasatta/geobit-chain for a redundant blockchain data provider
Topic: Blockchain API address balance response times from Italy (Read 1976 times)
BlockCypher just added gzip payload compression support simply by setting the "Accept-Encoding: gzip" HTTP header. This should greatly improve response times, especially for people using us from Europe or Asia.
Disclosure: I'm the founder and CTO at BlockCypher.
Disclosure: I'm the founder and CTO at BlockCypher.
Hi mriou,
we added the gzip header and noticed better response times.
Waiting to gather some data to be more statistically correct then i am gonna publish updated response times in the following days.
Thanks
BlockCypher just added gzip payload compression support simply by setting the "Accept-Encoding: gzip" HTTP header. This should greatly improve response times, especially for people using us from Europe or Asia.
Disclosure: I'm the founder and CTO at BlockCypher.
Disclosure: I'm the founder and CTO at BlockCypher.
Sorry, i haven't server spread across the world.... Not yet 
The better i can do is giving these ping results from my server to have an idea of the geographical distance:
The code and the server are the same for every endpoints so it's not really relevant to the test.
I can say that HTTP Request are made from a thread pool so they are not waiting each other.
The better i can do is giving these ping results from my server to have an idea of the geographical distance:
Code:
--- blockchain.info ping statistics ---
34 packets transmitted, 34 received, 0% packet loss, time 33054ms
rtt min/avg/max/mdev = 16.583/16.696/16.777/0.145 ms
--- btc.blockr.io ping statistics ---
40 packets transmitted, 40 received, 0% packet loss, time 39067ms
rtt min/avg/max/mdev = 17.946/18.102/18.328/0.181 ms
--- api.blockcypher.com ping statistics ---
320 packets transmitted, 320 received, 0% packet loss, time 319474ms
rtt min/avg/max/mdev = 20.980/21.693/22.470/0.425 ms
--- blockexplorer.com ping statistics ---
331 packets transmitted, 331 received, 0% packet loss, time 330548ms
rtt min/avg/max/mdev = 16.664/16.832/17.010/0.102 ms
--- api.biteasy.com ping statistics ---
38 packets transmitted, 38 received, 0% packet loss, time 55960ms
rtt min/avg/max/mdev = 16.750/16.966/20.020/0.547 ms
--- api.chain.com ping statistics ---
39 packets transmitted, 30 received, 23% packet loss, time 46887ms
rtt min/avg/max/mdev = 56.758/57.832/58.737/0.640 ms
--- helloblock-ssl.herokuapp.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4031ms
PING DISABLED
The code and the server are the same for every endpoints so it's not really relevant to the test.
I can say that HTTP Request are made from a thread pool so they are not waiting each other.
I find this a completely inaccurate test. Zero information is given about it and frankly it's impossible to measure response times by only using one server from one specific location in the world.
If you want you can share more information about it (code, setup, server details etc etc) so we can have a further look if required.
If you want you can share more information about it (code, setup, server details etc etc) so we can have a further look if required.
Hi,
i am asking balance of various bitcoin addresses to various blockchain API provider and i wanted to share response times achieved
The requests are made in round robin in a 3 day time span from a server located in Italy.
n is the number of request, m is the mean response time, v is the variance.
If others API developer would like their service to be included in the list, reply with you api reference docs and it will be added.
i am asking balance of various bitcoin addresses to various blockchain API provider and i wanted to share response times achieved
The requests are made in round robin in a 3 day time span from a server located in Italy.
Code:
n= 4174 m= 79 v= 223 min= 26 max= 3000 http://btc.blockr.io/api/v1
n= 4173 m= 256 v= 816 min= 42 max=20023 http://blockchain.info
n= 4170 m= 412 v= 703 min= 111 max=17432 http://blockexplorer.com
n= 4170 m= 419 v= 283 min= 232 max= 3332 http://mainnet.helloblock.io/v1
n= 4174 m= 463 v= 1377 min= 35 max=32070 https://api.biteasy.com/blockchain/v1
n= 4170 m= 496 v= 647 min= 129 max= 5131 http://api.blockcypher.com/v1/btc/main
n= 4167 m= 954 v= 1719 min= 114 max=20023 https://api.chain.com/v1/bitcoin
n is the number of request, m is the mean response time, v is the variance.
If others API developer would like their service to be included in the list, reply with you api reference docs and it will be added.
Jump to: