On Fri, Apr 15, 2011 at 4:17 AM, Alan <a...@malloys.org> wrote: > Holy cow wall of text. I really couldn't get through the whole thing, > but I scanned it and I don't see you mentioning output-stream > buffering, which would be one of my primary suspects for this sort of > behavior.
I didn't mention it because it isn't that. The println methods flush the output buffer. > Sorry if you've already considered this. As for why it > allocated a bunch of heap: if you tell it it can have a bunch of > memory, it won't bother to GC until it starts to feel pressure. So > even if you only have a 4K "main" object that you reuse, you may have > a lot of transient objects piling up because nobody is in a hurry to > clean them up. Yeah, a big chunk of my post was an attempt to estimate how much volume of such transient objects should have piled up, and it was nowhere near several tens of meg. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
