Chief Technology Officer at OXIA Khaled has posted 1 posts at DZone. View Full User Profile

Testing the Validity of Google App Engine Dashboard Data

  • submit to reddit

The DashBoard of Google App Engine presents interesting results, but what is the truth behind this data? I started by deploying a simple Java EE (JSP / Struts / Strus menu) and deploying it in the Google App Engine cloud at

To check the validity of  the values presented by the DashBoard of Google App Engine, we use a simulation tool in the classical world of performance studies: the famous Jmeter

Run a simulation of 20 concurrent virtual users (20 Threads).

The scenario is executed 100 times.

We note that at the beginning of the simulation

At the end of simulation the graph Request / Second becomes

The Google App Engine’s Dashboard allows you to track the behavior of the application.

Thus, after the full execution of the script, the results presented by the GAE's Dashbord are summarized as follows:

On the other hand, after the end of the execution of the script, the results presented by Jmeter are summarized as follows :

The results of Jmeter Vs results GoogleApp Engine


There is a good concordance of results (although it sure is a short simulation . For more detailed results, it must be remembered that performance measures should follow a statistical study and use the laws of large numbers)




client vue

GAE DashBord

Google's serveurs vue



















The results shown by Google are validated by the results of Jmeter

We can rely on the DashBord.


For this first test : it took me half an hour to deploy a simple old Struts based application on the Google cloud

No changes were necessary!  Note, there was no transaction, database, Spring, Hibernate..

The Google App Engine Dashboard allows monitor the activity of the application and see the logs and the response time.

Working with GoogleApp Engine is :

  • Easy
  • Allows recycling of "old" Java
  • The Dashboard provides information close to the reality and verifiable


Published at DZone with permission of its author, Khaled Ben Driss.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


AKIK Tarak replied on Thu, 2009/04/16 - 7:20am

Hi khaled,

that demo show us the powerful tool that google provide in order to test and simulate application response at real time..

but the sample test application seem to be weak and thin in memory use and CPU capacity.

in fact i have two questions :

-what would tests look like between google and Jmetter in a real application(transactional behavior)

-jmetter is used as a standalone application however google is a web tool that integrate as a proxy interceptor to the application or something like this..did this factor means something for tests?


Khaled Ben Driss replied on Thu, 2009/04/16 - 12:43pm in response to: AKIK Tarak

The aim is not a performance review, but check the quality of data submitted by the Google App Engine DashBorad

I used Jmeter to perform a simulation
Jmeter can calculate the number of request sent to the server
this allows to check the values displayed by Goggle

this is independent of the quality of the application.

jiji530 (not verified) replied on Tue, 2009/06/30 - 12:16am

thanks for your post.perhaps you will like abercrombie ed hardy mortgage rates tiffanys ed hardy Is not it?

Kenneth Wheeler replied on Fri, 2009/11/20 - 5:16am

I agree with what you said about Testing the Validity of Google App Engine Dashboard Data. Get Tall Testing the Validity of Google App Engine Dashboard Data. How to Grow Taller Naturally Testing the Validity of Google App Engine Dashboard Data. Growing Taller Secrets

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.