When running in production, we encounter significant issues
- Logs are stored in local storage. If the production runs behind a load balancer, the logs may never populate and encounter 500 errors because the request can hit a different server. The same goes for the in-memory database used to store
rake_tasks.
- Using
rake or bundle exec rake causes the entire application to load causing significant memory and CPU spikes.
Please let me know if these are planned. I would happily take each one and fix them with proper discussion.
When running in production, we encounter significant issues
rake_tasks.rakeorbundle exec rakecauses the entire application to load causing significant memory and CPU spikes.Please let me know if these are planned. I would happily take each one and fix them with proper discussion.