GLBSE CSV -> profit & loss calculator?

[lethe]

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

[1524628998]

1524628998

[1524628998]

1524628998

[1524628998]

1524628998

[1524628998]

1524628998

[1524628998]

1524628998

[Nefario]

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

This stops the server melting.

[sebnow]

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.

[EskimoBob]

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)

[Nefario]

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.