our app is awesome slow recently

176 views
Skip to first unread message

Robbie Cheng

unread,
Mar 3, 2013, 2:30:30 AM3/3/13
to Google App Engine, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
our app-id is :worldvision-tw
its response time is > 60s for the past week.

This is not acceptable, we would like ask for re-fund.

Thanks,

FrEaKmAn

unread,
Mar 4, 2013, 9:10:43 AM3/4/13
to google-a...@googlegroups.com, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
Hello,

I can also confirm that my clients app is also super slow. We are using Play Framework and it works ok. But there are few days when it's loading page for around 30 seconds which is too slow.

I demand some answers why it's working so slow!

alex

unread,
Mar 4, 2013, 9:47:12 AM3/4/13
to google-a...@googlegroups.com, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
How about profiling your app first and posting results here before
"demanding" any answers to questions that are probably really hard to
answer w/o a decenlty developed telepathic ability?
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengi...@googlegroups.com.
> To post to this group, send email to google-a...@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Andrin von Rechenberg

unread,
Mar 11, 2013, 6:49:54 PM3/11/13
to google-a...@googlegroups.com, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
Are you a heavy user of memcache? Our memcache shrunk by a factor of 10x since March 5th 2013.

Having a small memcache all of a sudden could explain your problem too.

Jason Collins

unread,
Mar 12, 2013, 5:14:44 PM3/12/13
to google-a...@googlegroups.com, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
We've noticed really poor memcache response times during the peak of the North American day - 80-120ms for a memcache.get() as fired by NDB (note this is the RPC time as visualized in appstats, so it does not include the deserialization costs).

The performance was so poor in fact that we disabled memcache for all of our NDB models. Datastore gets were the same or better in terms of response time - of course, they cost most $$ though. :(

This seems to be an order of magnitude worse in terms of performance than when memcache first started. It's too bad because it's hard to untrain memcaching habits, and memcache in general should be awesome.

j

Andrin von Rechenberg

unread,
Mar 15, 2013, 12:07:20 PM3/15/13
to google-a...@googlegroups.com, robbi...@gmail.com, ichu...@worldvision.org.tw, al...@mozilla.com
Any update on this from anyone?
Reply all
Reply to author
Forward
0 new messages