4 ms·

I'm trying and failing to imagine a situation where 30ms startup time would be a problem. Maybe some kind of network service that needs to execute a separate pr

by guelo 1y ago

I'm trying and failing to imagine a situation where 30ms startup time would be a problem. Maybe some kind of network service that needs to execute a separate process on every request?

deleted 1y ago
[deleted]
tacticus 1y ago
30ms is the absolute best case. Throw some spring in there and you're very quickly at 10s. rub some spring-soap and it's near enough to 60s
- ori_b 1y ago
  And imagine if you start adding sleep calls! Those could take minutes to hours, or even days!
  - ykonstant 1y ago
    New HN submission: How I Made My Sleep Function Accidentally Quadratic.
davemp 1y ago
30ms is pretty close to noticeable for anything that responds to user input. 30ms startup + 20-70ms processing would probably bump you into the noticeable latency range.
- yeasku 1y ago
  People play midi keyboards with 30 ms latency.
  - davemp 1y ago
    Yeah I don’t think 30ms is very noticeable, but say you have a cli tool with other 20-70ms to bump you up to 50-100ms your tool will have noticeable latency. Death by a thousand cuts.
pixelpoet 1y ago
It's not about how long someone is willing to wait with a timer and judge it on human timescales, it's about what is an appropriate length of time for the task. 30ms for a program to start, print hello world, and terminate on a modern computer is batshit insane, and it's crazy how many programmers have completely lost sight of even the principle of this.
- yeasku 1y ago
  Java is a tool, a very good one.