-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: Drop redis_socketio service #1382
Conversation
WARNING: Just a POC. You're free to modify your setup to test this out. Summary: - After this change bench wont generate config for redis_socketio instance. - Instead we set the same port as redis_cache service for use in socketio. i.e. both will share same instance. Code changes: - Config will have this difference: ```diff - "redis_socketio": "redis://localhost:12000", - "redis_cache": "redis://localhost:13000", + "redis_socketio": "redis://localhost:13000", + "redis_cache": "redis://localhost:13000", ``` - supervisord/systemd wont start redis_socketio service - for development setups: redis_socketio service is removed from procfile. Why? - Currently this redis instance is used only to ship messages from python to nodejs server... which is largely stateless (only pub/sub channels) - This change reduces 1 running process. Less resources for this ~= more resources for other running things. TODO: - [ ] decicisions - should we even do this? this should be optinal? - [ ] refactor progressbar in frappe - [ ] Tests - manual, FC, docker, automated - [ ] "migration" plan All dependent deployment projects will likely have to refactor their code to drop this service, shouldn't be too much work. Example: Frappe cloud, Frappe Docker.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
not finding time to finish it, also 5-10MB memory saving at max 😔 You can achieve this in your deployments just by doing the config change that I mentioned in description. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
🎉 This PR is included in version 5.17.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Good idea, but could have been backwards compatible |
@SaiFi0102 this is backward compatible AFAIK, unless you need 3rd service running for something else? |
I did a |
@SaiFi0102 #1481 this should fix it. |
Summary:
instance.
socketio. i.e. both will share same instance.
Code changes:
Why?
to nodejs server... which is largely stateless (only pub/sub channels)
resources for other running things.
All dependent deployment projects will likely have to refactor their code to drop this service, shouldn't be too much work.
Example: Frappe cloud (already done), Frappe Docker.