3 ms·
> compete in an area where garbage collection has its greatest competitive advantages (namely, long running server processes) I thought it was the opposite tha
by sovande 12y ago
> compete in an area where garbage collection has its greatest competitive advantages (namely, long running server processes)
I thought it was the opposite that was true. A garbage collector can/will leak memory over time (days) and will use up to 6-8 times more memory and can have performance problems etc. All long running server processes I know of (database, mail, http servers) manage their own memory. Exceptions are VM based systems and it is not unheard of to have a trivial Tomcat app use up to 1GB of memory.
- pjmlp 12y ago> A garbage collector can/will leak memory over time (days) and will use up to 6-8 times more memory and can have performance problems etc. Usually that is a consequence of not optimizing the applications. Using Java as an example, I still meet people that don't know about VisualVM, Mission Control, Eclipse MAT and many other similar tools. It is possible to write applications that exhibit a flat GC line after they are warmed up, but many don't bother until someone complains about.
- hga 12y agoMy, how times have changed. Here, I come from the Lisp world where PDP-10s had magnetic core memory, and a max of 1MiB (of 9 bit bytes) in address space. Lisp Machines used DRAM, but at least early on less than an address space (64MiB of 8 bit bytes), and keeping your working set inside that was an issue if for no other reason than GC by the time I showed up was incremental copying without generations (i.e. an increment of GC would tend to trigger a page fault). So I assure people like sovande that this can be done correctly, even if it's convenient to "ship it now!" and later find out what's "leaking" (keeping unneeded stuff from the tender mercies of the garbage collector).