[google-appengine] Re: Huge time difference for serving the same request
If a request a served by an instance that is alive for sometime, then it is fine. However, sometimes the request is directed to a new instance. Any first request for a new instance is adding a considerable delay. -Aswath On Sat, Sep 14, 2013 at 10:50 AM, timh wrote: > I would check that this is always the case. Also check what 3rd and 4th > request is like - make sure it's the same instance. > > If so it would then suggest that additional initialisation is being > performed that is expensive or that caching of some data (memcache for > instance) has a significant performance impact (improvement) for 2nd and > subsequent requests. > > You should use appstats to profile what this request is doing. > > T > > > On Saturday, September 14, 2013 1:05:49 PM UTC+8, aswath wrote: > >> I am attaching the new logs. >> >> I was examining the logs. It did not say, it started a new instance. >> But, there was a instance startup before that log >> /_ah/warmup 200 15380ms 0kb >> >> I noticed that the request that is taking longer was served by the newly >> started instance. >> >> >> -Aswath >> >> >> >> On Sat, Sep 14, 2013 at 9:48 AM, timh wrote: >> >>> You truncated the log for the 4159ms request. Did it say it started a >>> new instance ? >>> >>> T >>> >>> >>> On Saturday, September 14, 2013 11:15:37 AM UTC+8, aswath wrote: Hello, I am finding a huge time difference for serving the same request. Attached is the logs that shows the serving time for the same request. The same request was accessed with in 1 min interval from the same browser. There is no business logic change that happens between the first 1st request and the 2nd request. For the first request the serving the time is 4159ms, and for the second request it is 832ms. Why is this huge time difference? -Aswath >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: What is the best Python Framework for hosting on Google App Engine ?
to use Webapp2 framework in webapp2 framework all Google library support On Friday, 13 September 2013 11:40:25 UTC+5:30, Chitrank Dixit wrote: > > Hello Google Developers, > > We are developing a website on Google App Engine using Python. We have > analysed that the application would scale in the future and therefore we > want to use the best error free python web framework that should work on > NoSQL ( Redis, Datastore) and all other resources well. > > So using Django for Redis and NoSQL is still tricky as the application > produce lots of bugs and if using Django and not able to use the resources > it provides then it is better to use some other framework if we need to > make the whole DB. So the next framework we are looking for is Flask. > > We have used Heroku and DigitalOcean before but many great sites like > Udacity, Khan Academy inspires to use the Google App Engine. > > We are planning to start a Google Cloud Platform Project, So please let us > know that Flask would meet out needs or not. > > *Regards* > *Chitrank Dixit > * > *IIPS-DAVV > * > *Indore (M.P.) , India * > *MCA > * > *trackleech.blogspot.in* > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] in datastore not working any operator kind less query?
dbObj = datastore.Query("data", {}) # here data is table name
dbObj.Run()
count = dbObj.Count()
here count is > 0
but i find using operator in update method
filterObj = { key : value }
key = "id!="
value = "123"
dbObj.update(filterObj)
dbObj.Run()
count = dbObj.Count()
here, count is 0
here, operator = " <, <=, =. !=, >, =>"
but all operator not working
how to filter record without use GQLQuery and model class?
please somebody help
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Huge time difference for serving the same request
I would check that this is always the case. Also check what 3rd and 4th request is like - make sure it's the same instance. If so it would then suggest that additional initialisation is being performed that is expensive or that caching of some data (memcache for instance) has a significant performance impact (improvement) for 2nd and subsequent requests. You should use appstats to profile what this request is doing. T On Saturday, September 14, 2013 1:05:49 PM UTC+8, aswath wrote: > > I am attaching the new logs. > > I was examining the logs. It did not say, it started a new instance. > But, there was a instance startup before that log > /_ah/warmup 200 15380ms 0kb > > I noticed that the request that is taking longer was served by the newly > started instance. > > > -Aswath > > > > On Sat, Sep 14, 2013 at 9:48 AM, timh >wrote: > >> You truncated the log for the 4159ms request. Did it say it started a >> new instance ? >> >> T >> >> >> On Saturday, September 14, 2013 11:15:37 AM UTC+8, aswath wrote: >>> >>> Hello, >>> I am finding a huge time difference for serving the same request. >>> Attached is the logs that shows the serving time for the same request. >>> The same request was accessed with in 1 min interval from the same >>> browser. There is no business logic change that happens between the first >>> 1st request and the 2nd request. >>> >>> For the first request the serving the time is 4159ms, and for the second >>> request it is 832ms. Why is this huge time difference? >>> >>> -Aswath >>> >>> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Huge time difference for serving the same request
You truncated the log for the 4159ms request. Did it say it started a new instance ? T On Saturday, September 14, 2013 11:15:37 AM UTC+8, aswath wrote: > > Hello, > I am finding a huge time difference for serving the same request. > Attached is the logs that shows the serving time for the same request. > The same request was accessed with in 1 min interval from the same > browser. There is no business logic change that happens between the first > 1st request and the 2nd request. > > For the first request the serving the time is 4159ms, and for the second > request it is 832ms. Why is this huge time difference? > > -Aswath > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: What is the best Python Framework for hosting on Google App Engine ?
I have used pyramid a lot. For large sophisticated apps requiring the notion of scoped security there is not much that comes close. I have also built sophisticated apps using bobo/repoze.who/what (again authentication/authorization) in both cases these env's are not tied in any way to a particular backend. T On Friday, September 13, 2013 2:10:25 PM UTC+8, Chitrank Dixit wrote: > > Hello Google Developers, > > We are developing a website on Google App Engine using Python. We have > analysed that the application would scale in the future and therefore we > want to use the best error free python web framework that should work on > NoSQL ( Redis, Datastore) and all other resources well. > > So using Django for Redis and NoSQL is still tricky as the application > produce lots of bugs and if using Django and not able to use the resources > it provides then it is better to use some other framework if we need to > make the whole DB. So the next framework we are looking for is Flask. > > We have used Heroku and DigitalOcean before but many great sites like > Udacity, Khan Academy inspires to use the Google App Engine. > > We are planning to start a Google Cloud Platform Project, So please let us > know that Flask would meet out needs or not. > > *Regards* > *Chitrank Dixit > * > *IIPS-DAVV > * > *Indore (M.P.) , India * > *MCA > * > *trackleech.blogspot.in* > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] What is the best Python Framework for hosting on Google App Engine ?
I'm pretty happy with django-nonrel, but I don't have much to compare it to. It's nice because it comes with a few things to get you up and running quickly, like a test harness that you don't have to build yourself. Unfortunately, getting a live test server running with automated Selenium tests isn't quite there yet. The only big complaint is that it doesn't have ndb's automating entity caching. Also, you're not gonna get redis working easily on GAE regardless of the framework. It might be possible using the VM based backends though. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Processing search documents at scale
We have 50,000,000+ search documents that we need to change (i.e., delete the old version, create a new version). These are sharded across many individual indexes. I think the per-second rate limit for interacting with the search API is 50/s. We need to leave some room for live traffic, so if we clamp our re-indexing to 25/s, that means it will take 23 days to process all these documents. Does anyone have other ideas? Are there any tools coming out that would allow faster throughput? The ability to completely drop an index in one call might help: we could build up our new indexes, cut over to them, then drop the old ones in a single operation - this would at least cut the number of operations in half. Does anyone have any war stories about operating over search index documents at scale? Thanks, j -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: App Engine VM-based Backends - Trusted Tester Sign-up
All PHP project owners, please star https://code.google.com/p/googleappengine/issues/detail?id=9953 for introducing support for PHP VMRuntime. Thanks On Thursday, 29 August 2013 15:44:03 UTC+10, Takashi Matsuo (Google) wrote: > > > Hi Marcel, > > Currently VM-based backends support Java and Python2.7. > I'd appreciate it if you could file issues for supporting PHP and Go at: > > https://code.google.com/p/googleappengine/issues/list?can=2&q=Component%3DVMRuntime > > I'd like to know how many people have interests in it. > > Thanks for asking! > > -- Takashi > > > On Tue, Aug 27, 2013 at 3:37 AM, Marcel Manz > > wrote: > >> Will those VM-based backends support all runtimes? So Java, Python and >> PHP? >> >> -- Marcel >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengi...@googlegroups.com . >> To post to this group, send email to >> google-a...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/google-appengine. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Takashi Matsuo | Developers Programs Engineer | tma...@google.com > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
