Nikil
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Hey do you know if there's a limit on outgoing message size? That platform limits table only lists a limit for incoming messages (1MiB)
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
yea that sounds like more of a batching advantage rather than a gating advantage. I think this a comment more on the order they're introduced in the article.
What you described definitely sounds like a performance benefit
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Actually pretty much everything else made sense there. I come from an embedded systems background so similar singlethreaded concurrency handling
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
This mostly made sense but I'm confused about response gating. Is it only fast to do that because we're waiting to memory first before sending to user rather than to disc? Otherwise how's that any faster than awaiting the write
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Ah good point that whenever someone goes to a new chapter they'll need to read all the questions
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Is the DO storing this stuff on disc or in memory? The docs say unlimited so I'm assuming on disc?
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
I think ideally we should only write the vast majority of operations and read only in the cases where somebody joins a session, and then I guess we'll have to read if somebody upvotes a question so that we can read the current upvotes list and append the user to that list?
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Sounds like we should instead have something like
questions:<projectID>:<chapterID>:<questionID> as the keys, and each stores the data for only 1 question? So then the only slow operation would be the first load for a user where we need to fetch all the relevant questions.43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Cause we have to json.parse the stringified value
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Ya we were putting all the questions into one key called questions.
Must be contributing to latency too
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Relatedly, does the DO store need to be flat keys? Or can I have nested and access just one of the nested values?
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
I know what a Kibibyte is. Just didn't know where the # was coming from.
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
We basically host live office hours chats for various coding projects for our students across the country.
Each project has lets say 20 chapters.
A teacher needs to see all the questions for all the chapters so that they can answer.
A student may only need to see one chapter at a time I suppose.
Right now, we're creating a separate Durable Object for different projects (essentially a course).
Does it even make sense to section further?
43 replies
CDCloudflare Developers
•Created by Nikil on 1/3/2024 in #workers-help
Socket response time >=150ms ?
Wait so what does this actually apply to?
Storage is writing to a KV, right?
43 replies