Thank team Nomos for the contributions to this project.
I’m currently facing an issue: when the FastAPI server’s worker count is set to 1, the requests to “send a message to an existing session” are always blocked and executed sequentially.
From what I’ve researched, the problem seems to come from the fact that session.next() is written as synchronous (all methods in the Session class are synchronous).
As a result, the system cannot scale effectively, since the number of concurrent requests is limited by the number of available workers.
Please let me know if I might be mistaken here — I’d really appreciate your feedback.
Thank team Nomos for the contributions to this project.
I’m currently facing an issue: when the FastAPI server’s worker count is set to 1, the requests to “send a message to an existing session” are always blocked and executed sequentially.
From what I’ve researched, the problem seems to come from the fact that session.next() is written as synchronous (all methods in the Session class are synchronous).
As a result, the system cannot scale effectively, since the number of concurrent requests is limited by the number of available workers.
Please let me know if I might be mistaken here — I’d really appreciate your feedback.