4 ms·
What happened then? It was able to serve the site but not do API calls, so no mem-cache in front of your database? The Redis mem-cache didn't flush itself when
by gammateam 8y ago
What happened then? It was able to serve the site but not do API calls, so no mem-cache in front of your database? The Redis mem-cache didn't flush itself when full?
- kiechu 8y agoThe site is served via AWS CloudFront. It is SPA app hosted on S3. The API is on Heroku. No mem-cache anywhere. To search we use ElasticSearch hosted on AWS. We bump up the specs to speed it up but that was not the core problem. I suspect Heroku Postgres DB. We didn't used some Hobby version and I think it is the real bottle neck + some unnecessary middleware for the API that also requires DB.
- gammateam 8y agomaybe a mem-cache then? DB's have limited connections and are often billed as such, the mem-cache might help if there are any repeatable things. It might not be useful for your solution though since everyone searches for their own things all the time.
- kiechu 8y agoIncreasing DB plan did the job.