incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Kohler <>
Subject Re: Performance Tests - Suggestions and Ideas
Date Fri, 20 Nov 2009 14:12:18 GMT
Hi Vassil,
Sure, modern VM's are quite efficient for short lived objects, but they
still have limits as soon as you go multi threaded. Sun has IMHO send the
wrong message out in this regard.

Just one number, sending one short message (10 chars ?) caused  70 Mbyte to
be allocated in net.liftweb.textile.TextileParser$.toHtml(java.lang.String,
scala.Option, boolean)
 and  (probably) freed them afterwards. More details later ...


On Fri, Nov 20, 2009 at 2:49 PM, Vassil Dichev <> wrote:

> > Just as a teaser ;-)
> > The textile support is expensive in regards to the memory allocated
> (freed
> > afterwards).
> > Details will come as soon as I find some time.
> OK, no surprises there. For a single message there might even be more
> than one text area which is parsed by textile, as our own MsgParser
> must process the message first into text, hashtags, users and links.
> As you mentioned, the objects from the parse tree are short-lived
> though so I don't expect them to even leave the eden space on the Sun
> VM. Not sure how big a performance impact this will have.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message