esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: I'm just creating the users on the stax performance instance ...
Date Mon, 21 Dec 2009 13:38:21 GMT
Strange.  We should have really killer performance on the perf
instance, because we have our own dedicated amazon server with 1.7 GB
of memory.

The code base hasn't changed - I just restored an old snapshot of an empty DB.

> @Dick can we turn on New Relic on esmecloudperf?

Of course. Go ahead and activate it via the stax console.

D.

On Mon, Dec 21, 2009 at 2:08 PM, Markus Kohler <markus.kohler@gmail.com> wrote:
> Hi Ethan,
>  esmecloudperf.esme.staxapps.net/ was definitely much faster last week.
>
> I can also check this evening on my local instance, what is going on.
>
> @Dick can we turn on New Relic on esmecloudperf?
> I applied for an an evaluation account a few days ago.
>
> Regards,
> Markus
>
> "The best way to predict the future is to invent it" -- Alan Kay
>
>
> On Mon, Dec 21, 2009 at 1:44 PM, Ethan Jewett <esjewett@gmail.com> wrote:
>
>> 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 <hirsch.dick@gmail.com>
>> wrote:
>> > Should be fine.  The DB is empty
>> >
>> > On Sun, Dec 20, 2009 at 5:05 PM, Markus Kohler <markus.kohler@gmail.com>
>> 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
>> >>
>> >
>>
>

Mime
View raw message