> 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.
