Path: csiph.com!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!newsfeed2.funet.fi!newsfeeds.funet.fi!feeder1.news.elisa.fi!uutiset.elisa.fi!7564ea0f!not-for-mail From: Jukka Lahtinen Newsgroups: comp.lang.java.programmer Subject: Re: email stop words Organization: N/A References: X-no-archive: yes Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) Cancel-Lock: sha1:3i69l33xz4Dmw33XOsCaCYExt54= MIME-Version: 1.0 Content-Type: text/plain Lines: 13 Date: Thu, 21 Mar 2013 08:29:05 +0200 NNTP-Posting-Host: 91.155.89.249 X-Complaints-To: newsmaster@saunalahti.com X-Trace: uutiset.elisa.fi 1363847345 91.155.89.249 (Thu, 21 Mar 2013 08:29:05 EET) NNTP-Posting-Date: Thu, 21 Mar 2013 08:29:05 EET Xref: csiph.com comp.lang.java.programmer:23010 markspace writes: > Mine run to: I ended up making a lot more objects to avoid the immutable > Integer, and ended up using so much memory the garbage collector started > trashing. > Or, Integer shares low values (<127) and doesn't create new > objects. There's so many of those low numbers that this ends up saving > memory, and objects, in the long run (my biggest test case, in other Do you use new Integer(x) where you should use Integer.parseInt(x)? -- Jukka Lahtinen