They've made it clear that they care, they just haven't come up with a solution for Java initialization delays yet. App Engine for Python really does make the web faster. The problem is that they released their Java version before coming up with a way to either keep Java apps loaded or to load Java apps quickly.
Give them time; I'm sure they will have a solution eventually. Personally, I'm hosting my Java app with another hosting provider (rackspace cloudserver) until App Engine solves its Java performance problems. I will eventually move it back to App Engine for the scalability and cost benefits. On Mar 3, 7:48 pm, Robert Lancer <[email protected]> wrote: > Join the google dosent care about app engine performance club. To see > how much google dosent care just check out their own app engine status > page. > > http://code.google.com/status/appengine > > Isnt it funny how google lectures the whole world about how the web > should be "faster"? > > Also some things you can do do fix performance to make it as > slow(fast) as google app engine will allow. > > Override the DataStoreService interface making your own version that > logs each round trip to a console output. This will help you learn how > many round trips your making to datastore. Also google discourages > cron pinggers but with them not providing a decent solution who can > blame you. > > Also feel free to join my Google Please Fix App Engine For Java > facebook > grouphttp://www.facebook.com/pages/Google-Please-Fix-App-Engine-For-Java/3... > and post screen captures of your app failing! > > On Mar 3, 12:12 pm, infoatdfx <[email protected]> wrote: > > > > > I'm having a Google App Engine account for my applications, and I'm > > also an administrator of an application which was not created under my > > account. > > > The application that was not created under my account (but for which > > I'm an administrator) doesn't have much traffic yet, but when it goes > > live will probably have a few thousand requests per day. For now we > > are having a cron job running every minute to keep the application > > alive. But most of the time the cron job is not running on time. There > > is a red message that displays that the job was run 5 seconds or more > > too late. Even some cron jobs fail. With no traffic to my application > > (only the cron job running) the graph on my dashboard isn't a nice > > flat line with an average of 1 request per minute (0,0167 requests per > > second). We see a lot of peeks going from 0,005 to 0,02 requests per > > minute. > > > When I deploy the same application on my own account (greated a new > > application in my account but deployed the same webapp), the > > performance is like I would expect. With no traffic and only the cron > > job running we get a nice graph with 0,0167 requests per second. The > > line is almost flat and no cron jobs are running late. Even no cron > > jobs fail. > > > Also for simple request I see a performance difference between the two > > applications. I'm having a also a high CPU job that I need to run. > > This work am I doing with queues. When I execute the work in both > > applications, the slow application can only execute 3 to 4 tasks per > > minute, with the other one can run the same task with the same data 5 > > to 6 times a minute. > > > I would expect that both apps would behave in the same way and almost > > no notable performance difference, but this is clearly not the case. > > > Is anyone having the same issue? What can be done about this? How can > > I increase the performance of the "slow running application"? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
