3 ms·
I would say that CGI might be cheaper in terms of CPU usage on cloud, as on idle it does not use CPU more than the system. I wonder what is the "idle" cost of j
by p0w3n3d 3y ago
I would say that CGI might be cheaper in terms of CPU usage on cloud, as on idle it does not use CPU more than the system. I wonder what is the "idle" cost of java running spring for example. All I know is that if I run my application I am developing right now, the laptop I am using is trying to fly away (It's already warming up the engines), but it has also a postgres in another docker
- kevincox 3y agoAn idle persistent process doesn't use any CPU either (unless it has set up some background work) so there really shouldn't be much difference. I think at the extremes process-per-request and persistent processes look very similar. A fresh process will read data from the disk cache, but it may need to parse or transform that data before it is usable. A persistent process will have (some) pre-parsed data in memory. If you have swap enabled it will also be swapped out to disk if the process is idle. This may be faster if parsing that data into an in-memory structure is slow or slower if this results in more IO than the source data (which may be stored more efficently).