>Thanks - I really hadn't considered the fact that the call to readLine()
may be
>creating a lot of throw-away objects, too. I just saw that my loop was
creating
>one String object per iteration, so I thought, "That's not too bad." :)
:) been there... thought that too... then found out The Hard Way(tm)
that one string is also a fair amount of memory...
>I'm still confused, though, by the output from -verbosegc. When I ran it,
there
>was always a message at the same time as one of these 1-2 second pauses.
Made
>it obvious that gc had something to do with this. But the gc messages
claimed
>that the garbage collection took only a few milliseconds, while the
perceptible
>pause was at least a full second.
OK, how often did you see GC taking place? my test only ran about 2 min total
(it was `ls -lR /*` on 3/4 gig of fast dasd) but it caused over two dozen GCs
to take place (iirc 4 async, the rest alloc fails). did you see a lot of GC
work going on or was there only a few massive cleanups? (note to anyone with
access to the GC code: it would be _very_helpful_ if you would include the
system time (an unformated long is fine) within the "<GC:" info for later
analysis of this kind of thing... (hint, LINUX value add! ;) )
another thought... how heavily loaded is the system? and which threading model
are you using? I suppose it might be possible that the GC thread put the
working
thread to sleep and the scheduler(s) let some other thread work for a while
before resuming your working thread.... then again... :} that's starting to
sound a tad far fetched even for me late at night.....
!NEW!-=> <*> cabbey at home dot net http://members.home.net/cabbey/ <*>
"What can Microsoft do? They certainly can't program around us." - Linus
-----BEGIN GEEK CODE BLOCK----- Version:3.12 http://www.geekcode.com
GCS$/IT/PA$ d(-) s++:+ a-- C+++$ UL++++ UA++$ P++ L++ E- W++ N+ o? K? !P
w---(+)$ O- M-- V-- Y+ PGP+ t--- 5++ X+ R tv b+ DI+++ D G e++ h(+) r@ y?
------END GEEK CODE BLOCK------
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
