A couple times now I've had reports that the app is performing very poorly (slow, failed or timed out requests) and when I try to debug it by reproducing someone's queries, I notice that caching of both routes and travel times has invariably failed too.
No real ideas yet as to the cause of this. It's always probably ~ a week or two at least since I'd restarted the server... perhaps it's after an EC2 reboot that this happens? Something in that startup script?
A couple times now I've had reports that the app is performing very poorly (slow, failed or timed out requests) and when I try to debug it by reproducing someone's queries, I notice that caching of both routes and travel times has invariably failed too.
No real ideas yet as to the cause of this. It's always probably ~ a week or two at least since I'd restarted the server... perhaps it's after an EC2 reboot that this happens? Something in that startup script?