Skip to content
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

Use bjoern instead of uwsgi for lower resource usage #145

Closed
neuhaus opened this issue Oct 9, 2024 · 2 comments
Closed

Use bjoern instead of uwsgi for lower resource usage #145

neuhaus opened this issue Oct 9, 2024 · 2 comments

Comments

@neuhaus
Copy link

neuhaus commented Oct 9, 2024

Since Otterwiki targets small installs, have you considered using bjoern instead of uwsgi?
It should be fast and need less RAM.

@redimp
Copy link
Owner

redimp commented Oct 9, 2024

Hey @neuhaus! Thanks for suggesting bjoern, never heard of it before.

Currently I'm considering to remove nginx (and rendered unnecessary supervisord) from the image. This is discussed in #121.

The otterwiki:2.x.y-slim images works in this way, see Dockerfile.slim for the details.

Without nginx, the WSGI server used must be able to serve static files efficiently, which uwsgi can do amazingly well according to my benchmarks. This feature is not supported by bjoern, as far as I have seen. Serving the static files via Flask is unfortunately far too inefficient to be considered.

@redimp redimp closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@neuhaus
Copy link
Author

neuhaus commented Oct 10, 2024

Another solution would be to provide all static files in a volume so nginx can serve them, even when it's not in the container.
Most users will probably need nginx in order to provide more than one service per virtual host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants