search

raintank / raintank-docker

raintank docker images and dev stack DEPRECATED / UNMAINTAINED
https://blog.raintank.io/docker-based-development-environment/
16 stars 4 forks source link

better running of graphite-api #39

Closed Dieterbe closed 9 years ago

Dieterbe commented 9 years ago

i know in devstack we switched to gunicorn to use multiple CPU's but i often have to switch start_graphite.py to use app.run so that i can see errors in the log, but then i have worse performance (presumably, didn't check).

i know in chef stack we've recently changed how graphite-api runs so we have good performance and also error logs. but not sure about the specifics, @woodsaj can you do the same thing for dev stack?

woodsaj commented 9 years ago

You can get errors out of gunicorn by changing the log settings in /etc/graphite-api.yaml.

Just look at the conf on a Dev node. On 13 Oct 2015 11:53, "Dieter Plaetinck" notifications@github.com wrote:

i know in devstack we switched to gunicorn to use multiple CPU's but i often have to switch start_graphite.py to use app.run so that i can see errors in the log, but then i have worse performance (presumably, didn't check).

i know in chef stack we've recently changed how graphite-api runs so we have good performance and also error logs. but not sure about the specifics, @woodsaj https://github.com/woodsaj can you do the same thing for dev stack?

— Reply to this email directly or view it on GitHub https://github.com/raintank/raintank-docker/issues/39.