I blew up or created some circular reference because it's late and I had a lousy week... I'm not familiar enough with the code, but you have several objects whose creation should be moved to the top of your code. And a few places you should swap to mutable returns.
The mutable returns won't speed up startup, but will drop your memory usage significantly. Though it looks like a crap ton of memory is being allocated, more than should be needed, for what I can tell is going on. Do your logs have a lot of Soft Memory limit errors? There is what I would call a bug in GAE where if your only instance is killed by the Soft memory limit that the replacement instance loads really slow. I think because the pending request queue is transferred to the new instance. I think your biggest win would be in lazy creating the objects and classes that you don't use much. Next is Threading your large loops. Caching your Hashes. Changing your trims to vectors, and your Concats with + to use stringbuffer. Weak the stuff that is temporary variables so they don't get clung to. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
