*I hope Google is not counting on everyone enabling multithreading to make
this new model work.*
*If so, I'm afraid I'll reluctantly have to move from GAE. *
I volume tested my GAE web app using jmeter with and without GAE
multithreading enabled.
Hope others will confirm/refute my findings:
1000 user threads, each doing 100 web page requests that issue a couple of
backend datastore reads with sessions enabled:
- without multithreading
- 30-40 nodes
- average 3 sec response time
- only a few 500 errors
- with multi threading
- 3 nodes
- average 4 sec response time
- many 500 errors
*Summary: for my app (Java, Stripes, Slim3), multi-threading is slower and
less stable under heavy load, so I turned it off.*
*
*
--
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.
