--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/1A-gNBPyoo0J.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Comparing Instances of GAE to instances of EC2 is like Comparing a 5HP Briggs and Strat Engine to having 5 Actual 4 legged horses.
5 horses will haul 5 people a lot farther a lot faster than a gokart with 5HP, but no amount of Horses will accelerate an RC car to 60 Miles per hour.
Same for the Memory. Unless you have a set amount of data you know is going to be in “ram” you aren’t going to use “ram” you are going to use MemCache.
You aren’t going to use I/O so your hard drives aren’t going to chew CPU cycles so you can’t compare Cycle to Cycle.
Doing these kinds of comparisons will not help you develop good apps or plan for scale. Right some Skeleton code to do performance testing on a free instance. Examine how concurrency through the use of the API’s work.
Remember on an EC2 Instance you burn CPU cycles for everything from Network, SSL Computation, to Data processing. On GAE if you use the API’s the CPU sits idle or processes other threads.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/OdUu6hALckgJ.