Hmm ok I see, so I'm just using JDO without any frameworks on top of that, but as mentioned in the slim3 tests, JDO does add overhead (sometimes a significant amount). I don't plan to be doing any large queries (the slim3 example fetches 10,000 objects which I don't plan on doing at any point), but what is important to me is that startup time. One to two seconds is fine, four seconds starts pushing it, anything above that is pretty bad.
If we start using slim3 though, we lose the flexibility in moving to another host (not that I know of any that can compare to app engine) since it'll be interacting directly with big table instead of using jdo or jpa is an intermediate? Thanks On Fri, Jun 11, 2010 at 8:07 AM, Rahul <[email protected]> wrote: > Jake, > > Is there any official comments on this from google which says that it > discourage the pinging every 60 seconds or so. > > Also if we have some framework which we will always like to have if > doing some production application then what is the way out. > > Thanks, > Rahul > > On Jun 11, 10:16 am, Jake <[email protected]> wrote: > > Hi Mark, > > > > Yes, you can do better than 4.5 seconds without a framework. Also, > > there are layers that can be placed over the low level datastore (e.g > > Objectify) that add ease-of-use without noticeable additions to the > > startup time. > > > > The 60 second pinging thing is, indeed, done by some users and is > > officially discouraged by Google. At one point, I set up a similar > > pinging feature and found that it really didn't work. Theoretically > > it should, but the pings just caused loading requests every minute or > > so, which simply reduced the likelihood that a user would see the > > loading request; it didn't solve the problem. > > > > Jake > > > > On Jun 11, 7:32 am, Mark <[email protected]> wrote: > > > > > > > > > Hi, just joining in, trying to sum up: > > > > > In the best case (if we only use the low level datastore + no > > > frameworks on top) we can only hope that a fresh restart of our app > > > will take 4.5 seconds? > > > > > However if at least one user is hitting the site every 60 seconds from > > > somewhere in the world, then our app should be kept alive and no need > > > for restarts? > > > > > Not that I'm planning on doing it, but what prevents developers from > > > simply pinging the site every 60 seconds to force the app to stay in > > > memory? I ask what prevents it because if I play by the rules, I'm > > > going to get penalized if other developers are 'cheating' and doing > > > the artificial pinging, > > > > > Thanks > > > > > On Jun 9, 5:49 am, Jake <[email protected]> wrote: > > > > > > Hey Tin, > > > > > > Several people were using GAE's built in timing mechanism to ping the > > > > server to accomplish the same thing. Google came out and officially > > > > discouraged this as it tends to throw off any attempts they are > > > > currently making to fix the problem. I can't tell people what to do, > > > > but I opted to stop using this hack in the hopes that they will solve > > > > the problem. > > > > > > Besides, you'll notice that this hack doesn't really work over the > > > > long run. It will essentially restart your server every minute and > > > > won't really prevent the loading request from falling on your users > > > > instead of on your ping. > > > > > > Jake > > > > > > On Jun 8, 1:54 pm, Tin <[email protected]> wrote: > > > > > > > Hi all: > > > > > > > We have found a temporary solution for this issue: > > > > > Try with an AJAX timer kicking the server (doing nothing), maybe > one > > > > > request per minute (or less) and GAE will keep our site / users in > the > > > > > same node. > > > > > In our testing it could avoid the GAE web instance reloaded, but if > > > > > the request interval is long, it would cause another Datastore > > > > > performance issue:http://goo.gl/98zkthatwillbefixed in near > > > > > future. > > > > > > > More info please refer to here:http://goo.gl/mzQR > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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.
