I’m facing an issue with the Realtime Stream Chunks Overloaded problem. I’m using the OpenAI chatcomplete API in my function and getting the response as streaming chunks. When I receive the chunks, I update a specific document on the DB and subscribe it in the client at every change. The issue I’m facing here is that updating the document for every chunk takes longer than getting all chunks without updating it. For example, if I get the chunks without updating the stream document for the real-time connection, it takes only 3 seconds. However, when I use Realtime, it takes about 13 seconds. Can I use another way to handle real-time without updating and writing the chunks in Appwrite, such as websockets or something else?
However, when I use Realtime, it takes about 13 seconds.
Can you clarify what exactly is the 13 seconds? Is that the time it takes to update the document and receive all the chunks (in the function)?
It's the time it takes to update the document only for all chunks. My problem is that I need to establish a real-time connection between the server and the client directly without writing to the database but the available channels on Appwrite are limited. Therefore, I chose to write to a specific document in the database and subscribe to it at the client.
This operation takes more time during function execution and needlessly burdens the server with additional operations. So is there a way to establish a real-time connection between the server and the client directly for every user?
??
no
Recommended threads
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- i am getting 404 not found in my current...
in my current appwrite i am getting 404 not found from backend side and in frontend getting error of CORS error as backend is not working
- How to create a custom authentication sy...
I’m looking to create an Appwrite function that first verifies a client using some custom logic, like providing a secret key. Once this verification is complete...