Replies: 2 comments 2 replies
-
Yes, I tried gunicorn as well. It made no difference at all. I also tried different setups how nginx and uvicorn using one global socket or one socket per workers. I tested unix sockets vs. http sockets. nginx is better able to distribute load over multiple workers. But again none of this made any difference to the final performance. The bottleneck is clearly with SQLAlchemy and the database. I just recently became aware of this tweet by the developer of psycopg from December: https://twitter.com/psycopg/status/1606390672277311501 where he complains about threads inexplicably slowing down each other. The symptoms look very similar. So it might be something to follow up on. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the detailed response. Good to know that the bottleneck is already identified. |
Beta Was this translation helpful? Give feedback.
-
I stumbled upon your blog post benchmarking the new Python codebase: https://nominatim.org/2023/04/03/reverse-performance.html
Did you also test it in combination with gunicorn?
https://www.uvicorn.org/deployment/#gunicorn
Beta Was this translation helpful? Give feedback.
All reactions