4 ms·
Personally found Java's GC to be a little tricky but generally awesome. However, 100, even 200ms pauses get "lost" during network coms. But users tend to notic
by mSparks 10y ago
Personally found Java's GC to be a little tricky but generally awesome.
However, 100, even 200ms pauses get "lost" during network coms.
But users tend to notice if a page takes 30 seconds to load rather than 1 second (differences i've seen optimising Javas GC, don't know at all how Go and Java compare).
That kind of difference would be very expensive to solve using more servers.
- pjmlp 10y agoThe biggest issue is on single deployments like desktop or embedded, hence why these kind of improvements are so relevant.
- mSparks 10y agoThat's the key trade of these days in software imho. What kind of memory management you need. Sever side zero memory leaks absolute requirement and "real time" responses rarely a requirement. triggering gc during init and/or shutdown of a component often enough. Building a CNC machine - every tick is valuable, but as long as it can run a job for 2 days before crashing no one will notice if it leaks memory like a sieve when you run a calibration routine.