Worried about cold start | Deno | Page 1

patent token Dec 3, 2024, 12:04 PM

#

Hey, I am planning to move from DigitalOcean+Express to Hono+Deno+DenoDeploy, I have around 4k-6k requests per day (very predictable traffic). I am worried about cold start problem. Currently only my pricing page is on Deno Deploy (200 requests per day), and I see 1s delay or so, but I beleive it is because pricing page is not used that often.

Am I correct in my assumption that with more requests cold start is going to be less of an issue?
How fast is Deno Deploy accomodates for change in number of requests? My current understanding is that Deno Deploy spins up nodes in advance and predicts the traffic.

patent token Dec 19, 2024, 4:36 PM

#

Unfortunately I believe I have to move from Deno Deplay because of the cold starts. No support here, nor in this issue:
https://github.com/denoland/deploy_feedback/issues/505

frail locust Dec 19, 2024, 7:58 PM

#

Did you try on #deploy™ ?

patent token Dec 21, 2024, 11:43 AM

#

moved back to DigitalOcean, but still keeping Deno itself, plan to try Deno Deploy again some time in future
https://docs.deno.com/examples/digital_ocean_tutorial/

Deno

How to deploy Deno to Digital Ocean

In-depth documentation, guides, and reference materials for building secure, high-performance JavaScript and TypeScript applications with Deno

patent token Dec 21, 2024, 12:02 PM

#

Initially I thought that Deno Deploy would be better for my small enterprise, but eventually it becomes a problem of reducing the size of my npm dependies which is just out of scope for my project for now (not a frontend developer). Also apart from having cold start problem it actually worsenes the UX, since my database is in US and having Deno spawning next to the user actually increases time it takes to get data from db, since I am doing multiple of such requests before get the response to the user.

#

Most probably I am just a newbie and done something wrong, but meh.

minor summit Dec 21, 2024, 3:41 PM

#

Distance between DB server and Web Server is an issue for all Edge hosting approaches (not Deno deploy specifically). One solution is a colocated/replicated data store (e.g Deno KV).

exotic vector Dec 21, 2024, 3:44 PM

#

Kv as server-side local-first

patent token Dec 21, 2024, 9:11 PM

#

minor summit Distance between DB server and Web Server is an issue for all Edge hosting appro...

Yeah, totally agree, not saying that Deno to blame here, this is an issue of my app design

patent token Dec 21, 2024, 9:12 PM

#

minor summit Distance between DB server and Web Server is an issue for all Edge hosting appro...

Well, replicating data store seems like overkill for my app tbh, maybe on later stages

#

Oh, okay, it is time for me to sleep, you meant moving my user data into KV store. Interesting, I will try it in future!

#Worried about cold start