> 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.
Right, if all of your cores wait while the GC is running, that's tough. The concurrent collector might help a bit. > 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 ... Ugh, that's way too much indeed. Is it just when running the TextileParser the first time or every time a message is sent? You got me interested.
