Bitcoin Forum
December 10, 2016, 02:58:50 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  

Warning: Moderators do not remove likely scams. You must use your own brain: caveat emptor. Watch out for Ponzi schemes. Do not invest more than you can afford to lose.

Pages: « 1 [2]  All
  Print  
Author Topic: GLBSE CSV -> profit & loss calculator?  (Read 3035 times)
lethe
Jr. Member
*
Offline Offline

Activity: 51


View Profile
August 06, 2012, 11:01:55 AM
 #21

For me the API calls to GLBSE always timeout or 503, aborting execution.

The author has updated the fetchTicker macro (with a cached api fetch) but the update would need to be put into P&L calculator too.

link to git: https://github.com/znort987/glbse-googledoc-macro

"I have a bit in Bitcoin"
1481381930
Hero Member
*
Offline Offline

Posts: 1481381930

View Profile Personal Message (Offline)

Ignore
1481381930
Reply with quote  #2

1481381930
Report to moderator
1481381930
Hero Member
*
Offline Offline

Posts: 1481381930

View Profile Personal Message (Offline)

Ignore
1481381930
Reply with quote  #2

1481381930
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481381930
Hero Member
*
Offline Offline

Posts: 1481381930

View Profile Personal Message (Offline)

Ignore
1481381930
Reply with quote  #2

1481381930
Report to moderator
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
August 06, 2012, 12:42:11 PM
 #22

There is a limit on 10 requests to the API every minute.

This stops the server melting.

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
sebnow
Jr. Member
*
Offline Offline

Activity: 33


View Profile
August 06, 2012, 01:12:21 PM
 #23

There is a limit on 10 requests to the API every minute.

This stops the server melting.

Is this a global limit or per-IP? I'm having the same issues but I've restricted to less than 10 requests every minute. I understand GLBSE is getting pounded, but there's no point having an API if no one can really use it.

Donations: 1LTzmaxiDxWefd2kxED3j53du7uv8hFYL7
BitcoinPyramid
Put.io is a storage service that retrieves and puts files into your personal, private online space. Try it for free.
EskimoBob
Legendary
*
Offline Offline

Activity: 910


Quality Printing Services by Federal Reserve Bank


View Profile
August 06, 2012, 01:17:08 PM
 #24

There is a limit on 10 requests to the API every minute.

This stops the server melting.

At the moment, probably every API request hammers your db. Change it from "pull" to "push" and you can serve a huge pile of requests with no problems. Upgrade the API so it's not responding to every request with db query but answers with a pre-generated "statick page" - page that changes only when trade happens.
(4)

While reading what I wrote, use the most friendliest and relaxing voice in your head.
BTW, Things in BTC bubble universes are getting ugly....
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
August 06, 2012, 05:35:07 PM
 #25

There is a limit on 10 requests to the API every minute.

This stops the server melting.

That's because each API calls hits the DB.

If the caching was done at GLBSE instead
of client side, that would lighten the load
quite a bit.


Some parts of some API calls are cached, others not. Currently working on both graphs and API for some major improvements.

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!