Update: I've tried running 2 dynos to see if splitting traffic in two would reduce the slope of my memory leak, and also to see if the garbage collector would somehow work better.
It seems not : 2015-02-01T09:23:50.049734+00:00 heroku[web.1]: *source**=web.1* dyno=heroku .28228261.c4fede81-d205-4dad-b07e-2ad6dcc49a0f sample#memory_total=242.09MB sample*#memory_rss=236.50MB sample#memory_cache=5.59MB* sample#memory_swap=0.00MB sample#memory_pgpgin=97398pages sample#memory_pgpgout=35422pages 2015-02-01T09:23:38.787009+00:00 heroku[web.2]: *source**=web.2* dyno=heroku .28228261.9b8464db-9ab7-42e3-a61a-604a765f38be sample#memory_total=239.23MB sample*#memory_rss=233.64MB sample#memory_cache=5.59MB* sample#memory_swap=0.00MB sample#memory_pgpgin=95938pages sample#memory_pgpgout=34694pages The memory seems to grow at the same rate, regardless of the traffic being split between dynos. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
