Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Jim Janney Newsgroups: comp.lang.java.programmer Subject: Re: Java daemon Date: Mon, 12 Nov 2012 14:24:33 -0700 Organization: don't play chess with your daughter Lines: 17 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx04.eternal-september.org; posting-host="75975abe3fe3503ca7350803ab98e478"; logging-data="3930"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+dlkBnIyszrwROc8YcFEEe" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:uwVy1p8WF6VCuj4lUVIICKudsbw= sha1:RoBaJHu1xZbykvri+GJhSL9fT+o= Xref: csiph.com comp.lang.java.programmer:19718 "sl@exabyte" writes: > I gather that PHP daemon suffers from memory leak problem due to its garbage > collector mechanism. > > Since java also adopts the garbage collector mechanism, would java daemon > suffers from the same memory problem ? Probably not: not all implementations of GC are equal, and you can't generalize from one to another. For what it's worth, Twitter is in the process of migrating from Ruby to Java due to problems with memory management, and claims to be happy with the results: http://www.theregister.co.uk/2012/11/08/twitter_epic_traffic_saved_by_java/ -- Jim Janney