-
Notifications
You must be signed in to change notification settings - Fork 5
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
high runtime fees #13
Comments
No specific workaround is known. I am getting more requests than are covered in jamsocket/y-sweet#203, but the connection time has not increased to this point. I will respond to what I know about what is being discussed in this issue
DurableObjects' odd usage timeHere is the LastWeek usage of my public https://yjs.napochaan.dev. What you can save money by using Hibernation API.
It is described like this. Duration time even after WebSocket is closed.In my environment the connection appears to be closed. DurableObjects billing documentationSee here Examples 2, 3 and 4 are very expensive. The number of people using the system and the amount of time they are connected may lead to high bills. |
I had no knowledge of DurableObjects' high billing. I have not applied |
Loving this project, thanks for publishing!
Have you found a way around this issue? jamsocket/y-sweet#203
The text was updated successfully, but these errors were encountered: