I agree that the esmecloudperf.esme.staxapps.net/ instance is pretty slow. It takes almost 15 seconds between hitting the "Update" button and seeing the message show up in my timeline.
My recollection was that http://esmecloudserverapache.dickhirsch.staxapps.net/ was a lot faster when I tested it out last week, leading me to believe that we've had a bit of a performance regression in more recent builds. That's just a guess though. Just now I went into http://esmecloudserverapache.dickhirsch.staxapps.net/ and posted a couple of messages, and that instance now also takes almost 15 seconds for a new message to show up in my timeline. It seems like we probably have a bit of an issue we need to look into. If I can find the time today, I'll try to recreate locally and identify a specific commit that caused the issue. If anyone has a specific idea of what might cause this, that may lead to a faster resolution. Ethan On Sun, Dec 20, 2009 at 7:09 PM, Richard Hirsch <[email protected]> wrote: > Should be fine. The DB is empty > > On Sun, Dec 20, 2009 at 5:05 PM, Markus Kohler <[email protected]> > wrote: >> ... >> >> It works, but it seems to be a bit slow. >> Maybe it's my DSL? >> >> Regards, >> Markus >> >> "The best way to predict the future is to invent it" -- Alan Kay >> >
