Re: [google-appengine] Re: Spring MVC + GAE = slow startup
>> > > controller >> > > > simply forwards to JSP file with text. Deployed and the page got >> > > displayed >> > > > after 13 seconds. >> > >> > > > I knew the Spring with all proxies and scanning is not optimal for >> GAE >> > > but >> > > > I wasn't expecting this at all - it seems like the app have issues >> with >> > > > simple loading the libraries as I can see how the memory of >> instance is >> > > > growing by 1 MB per second. I've tried to: >> > >> > > > 1) merge jars into 3-4 bigger ones >> > > > 2) disable annotations (just for the test as with new spring mvc >> its >> > > quite >> > > > hard to do some better mapping only in xml) >> > > > 3) lazy load some spring beans >> > >> > > > And I can save like 5-10 secods from those 50+ seconds of my >> startup - >> > > is >> > > > it really so bad for everyone or is there some magic setting? >> > >> > > > Whats your normal startup time of your spring based app? > > -- > 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/-/wzMKMUqjlQgJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Need help or consulting: Request was aborted errors
I hope the fact that "paid" scheduler is better than "free" scheduler is not true. What about "try before you buy" principle for the free quota? On Tue, Jul 10, 2012 at 7:18 AM, Kyle Finley wrote: > Jeff, Thanks for the clarification. It's good to know that this is a free > quota issue. The fact that the errors are not reported in the logs, makes > it difficult to diagnose. > > -- > 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/-/LE6uvPsseWMJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Should developers pay for the useless instances? Can we set max instances to 1?
The feature can be optional, right? People who want unbounded number of instances can disable that feature. To me, it doesn't make sense that it is impossible to limit number of active instances when you are paying for that. On Wed, Jul 11, 2012 at 8:06 AM, alex wrote: > What's the point in using AE infrastructure then? You're probably better > off to EC2 micro instance, or openshift, or cloudfoundry, or appfog, or > heroku, in that case. > > Personally, I'd be -1 unstarring (if I could) such a feature. > > -- > 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/-/Ecu4sDu46WkJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] appengine with spring mvc and sitemesh
Have you try check the logs on admin console? On Sun, Jul 15, 2012 at 12:24 AM, Slawek wrote: > Hello, > I have created simple application using spring mvc and it works well both > my local computer and app engine. Next I have added sitemesh framework and > it work well only on my local machine, on app engine is only empty page > without code. I used spring mvc 3.1.1 and sitemash 2.4.2. I haven't idea > what should do to start application on app engine. > Best Regards > sw > > -- > 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/-/tzu-kFjy1VAJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Startup time exceeded...on F4?!
be, if you have longer backend tasks, > > putting those tasks into another version, in order to avoid blocking > other > > frontend requests. If you use python2.7 runtime with concurrent request > > enabled, probably you'd better isolate CPU bound operations from > user-facing > > frontend version in order to avid slow-down in the frontend version. > > > > Probably it is great if we offer an API for dynamically configuring the > > performance settings especially in terms of cost efficiency, and I think > > it's worth filing a feature request. > > > > -- > > Takashi Matsuo > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Startup time exceeded...on F4?!
Really, looking forward to see reply from Googler(s) regarding this. On Thursday, July 19, 2012 12:11:27 AM UTC+2, Michael Hermus wrote: > > I certainly appreciate the attempted explanation. Correct me if I am > wrong, but what you said amounts to this: > > Google has to route requests to cold start instances because otherwise, >> for large scale apps, the pending queue might get way too big, not to >> mention it could blow up sometime. >> > > If that is true, I suppose I would be quite surprised, for the following > reasons: > > a) Google's entire infrastructure is designed for EVERYTHING to scale > massively and still work well. > b) By waiting for instances to warm up first, I don't think you would > really increase the maximum depth of the pending queue by a whole lot. In > fact, the larger your app (i.e. the more instances you have active), the > less impact it would have relative to the alternative. > c) I don't think the pending queue is 'hosted' on a single machine; I am > pretty sure it relies on a resilient queue infrastructure designed to > tolerate failures and scale well. > > > On Wednesday, July 18, 2012 5:07:04 PM UTC-4, hyperflame wrote: >> >> On Jul 18, 2:38 pm, Michael Hermus wrote: >> > I dont believe that you (or anyone) has sufficiently explained how >> sending user requests to cold instances is ever better than warming it up >> first.. Said request can ALWAYS be pulled right off the pending queue and >> sent to the instance as soon as it is ready. >> >> Let me take a shot at this. Brandon Wirtz touched on it before, when >> he said "I agree that the Queue is sub optimal, but it is more sub >> optimal the smaller you are. When you get to 50 instances it is >> amazing how well the load balancing works. " >> >> Suppose you have a massive store (we'll call it MegaWalmart). >> MegaWalmart has 100 staffed checkout lanes. Suppose all of these lanes >> have a single queue of people lined up, and a supervisor which sends >> customers to open checkout lanes (roughly analogous to your preferred >> way of handling GAE request queuing). That one line would be huge, >> would block traffic around the store, etc. It's far better, from >> MegaWalmart's POV, to have multiple check out lines, one line per each >> lane. >> >> Now suppose you have another checkout lane open up. (remember, now we >> have one line per lane) That's an additional 1% capacity. Now if the >> checkout clerk is drunk/hungover/whatever, that additional lane will >> take extra time to open, annoying the customers lined up in that lane. >> From MegaWalmart's POV, who cares? Less than 1% of your customers were >> inconveniced. 99% of people still had a decent time checking out. >> >> Let's apply this to the scheduler. Suppose there was one single queue >> of requests. At Google-scale, that queue of requests could easily >> exceed millions of entries, possibly billions. And God help you if the >> machine hosting the queue gets a hiccup, or an outright failure. Don't >> you agree that, at least at Google-scale, requests should immediately >> be shunted to instance-level queues? Even if a single instance takes >> forever, or fails, we don't have to care: such a failure would only >> affect 0.01% of users. >> >> This leads me to my final point: My understanding, from reading the >> documentation and blog/news posts about GAE, is that the the core of >> GAE is ripped pretty much directly from production Google services. >> The problem with this is, the scheduler is intended to work at very >> high scale, not at low scale. And frankly, this makes sense when you >> consider a lot of the finer points of the GAE ecosystem. >> >> So, to fix this: GAE needs to have a good relook at scheduler code, >> and rewrite it so that it has two different rules for apps at less >> than 50 instances, and more than 50 instances. Additionally, perhaps >> the GAE should look at making the scheduler smarter; perhaps it could >> measure the startup time of instances, and in the future, not send >> requests to cold instances until that startup time has elapsed. >> >> Personal thoughts: I have admined a corporate GAE app that has >> exceeded 100 instances, and I use GAE for personal apps that use, at >> max, 3-4 instances. When you use GAE at these two extremes, you really >> get an understanding of how GAE scales. For instance, a personal >> anecdote: for my low end apps, I occasionally notice that GAE starts >> up a new idle instance. I'm not charged for it, it doesn't do any >> work, but it is counted in the "current instances" counter. My guess >> is that, during non-peak times, the GAE scheduler will load into >> memory additional instances of low end apps, to try and be ready for >> quick scaling. So I believe the GAE team tries to handle low-end >> instances, but it does need more work. >> >> TLDR: the scheduler needs more work, and MegaWalmart is the same thing >> as Google's schedul
Re: [google-appengine] Re: Huge difference (8,400%) between billing received and information in the dashboard
Hello Kate, I believe you have enabled billing. $2.10/week or about $9/month is a minimum charge. On Mon, Jul 23, 2012 at 6:02 PM, kate wrote: > I'm searching for a very similar issue - I've been charge $2.10/week for > no activity, and there is nothing on my billing that includes the > $2.10/week minimum - is this something that applies to all app engine > accounts? I can't find documentation of it anywhere in the information I've > received. > > Thank you. > Kate > > On Thursday, June 14, 2012 11:53:55 PM UTC-7, hugues2 wrote: >> >> Hi Greg, >> >> Thanks for your very fast feedback. Indeed I completely overlooked the >> weekly charge of 2.10$. >> >> Sorry for the big mistake. >> >> Hugues >> >> >> Le vendredi 15 juin 2012 08:30:46 UTC+2, hugues2 a écrit : >>> >>> Gi, >>> >>> Has anyone the same issue ? >>> >>> --> In the admin dashboard, I see that I should be billed 0,03 $ (see >>> below, Annex 1) >>> >>> --> I received a billing for 2,54$ (see below, Annex 2) >>> >>> ==> Difference of : 8,400% >>> >>> Also the number of instance hours has a 100% difference between the >>> dashboard (15.62) and the billing (33.42) >>> >>> ==> Which information is the correct one ? >>> >>> *Annex 1 : Dashboard :* >>> >>> >>> Frontend Instance Hours15.62 Instance Hours0.00$0.08/ Hour$0.00Backend >>> Instance Hours0.00 Instance Hours0.00$0.08/ Hour$0.00Datastore Stored >>> Data0.04 GBytes0.00$0.008/ GByte-day$0.00Logs Stored Data0.00 >>> GBytes0.00$0.008/ >>> GByte-day$0.00Task Queue Stored Task Bytes0.00 GBytes0.00$0.008/ >>> GByte-day$0.00Blobstore Stored Data0.02 GBytes0.00$0.0043/ GByte-day >>> $0.00Datastore Write Operations0.03 Million Ops0.00$1.00/ Million Ops >>> $0.00Datastore Read Operations0.09 Million Ops0.04$0.70/ Million Ops >>> $0.03Datastore Small Operations0.00 Million Ops0.00$0.10/ Million Ops >>> $0.00Outgoing Bandwidth0.01 GBytes0.00$0.12/ GByte$0.00Recipients >>> Emailed10$0.01/ 100 Recipients$0.00Stanzas Sent00$0.10/ 100K Stanzas >>> $0.00Channels Created >>> [image: 0%] >>> 0%0 of 95,0400$0.01/ 100 Opens$0.00Estimated cost for the last 23 hours: >>> [image: 1%] >>> *$0.03* / $2.00* >>> >>> >>> >>> >>> >>> *Annex 2 : Billing : * >>> >>> ResourceUsedCharge*Frontend Instance Hours* >>> $0.08/Hour33.48$0.00*Discounted Instance Hour* >>> $0.05/Hour0.00$0.00*Unused Discounted Instance Hour* >>> $0.05/Hour0.00$0.00*Backend Instance Hours* >>> $0.08/Hour0.00$0.00*Datastore Storage* >>> $0.008/GByte-day0.30$0.00*Logs Storage* >>> $0.008/GByte-day0.03$0.00*Taskqueue Storage* >>> $0.008/GByte-day0.00$0.00*Blobstore Storage* >>> $0.0043/GByte-day0.14$0.00*Datastore Writes* >>> $1.00/Million Ops0.02$0.00*Datastore Reads* >>> $0.70/Million Ops0.05$0.00*Small Datastore Operations* >>> $0.10/Million Ops0.01$0.00*Bandwidth Out* >>> $0.12/GByte0.03$0.00*Emails* >>> $0.01/100 Recipients0.05$0.00*XMPP Stanzas* >>> $0.10/100K Stanzas0.00$0.00*Opened Channels* >>> $0.01/100 Opens0.00$0.00*Minimum Spend* >>> $2.10/Week$2.10*Total:*$2.10 >>> >>> >>> >>> >>> -- > 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/-/BRuuZnpE5KAJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Differentiated service with Google App Engine
Hello, Anyone have an idea on how to achieve a differentiated service with Google App Engine? I have two types of users. One is premium while another one is free user. I would like to set different minimum latencies for firing up new GAE instances between the two. In other words, I am willing to pay extra for the traffic generated from the premium users. Nonetheless, for the free users, I would prefer to pay at minimum or within the daily free quota provided by Google. In my case, I expect that the free users are able to tolerate higher latency than the premium ones. I believe that this case should be quite general and apply to many people. Assuming that I can identify types of users by the URLs they use or via other mechanisms. The only way I could think of is creating two separated applications and letting the premium users access the one that enables billing, while free users access the one that doesn't. However, my free and premium users need to share the datastore because they are also have to communicate within the application. Unfortunately, it seems that sharing a datastore across applications is not possible at the moment (feel free to correct me if I am wrong). Any ideas or suggestions? Cheers, Rerngvit -- 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/-/i3ZBDg4VWD4J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Error while installing the google plugin for eclipse
Hello, Have you check whether you have a connection problem? Have you try command below on shell? $ wget http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.appengine.eclipse.core_3.0.1.v201206290132-rel-r42.jar On Thu, Jul 26, 2012 at 3:53 AM, sai krishna haridass < sharidass1...@gmail.com> wrote: > > I am receiving the following error while installing the goolge app enginge > plugin 1.7 for eclipse juno 4.2. I have tried couple of times but it > throws same error after installing 40% > Please advice me. > > An error occurred while collecting items to be installed > session context was:(profile=epp.package.jee, > phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, > action=). > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.appengine.eclipse.core_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://googleappengine.googlecode.com/svn/trunk/java/updatesite/plugins/com.google.appengine.eclipse.sdkbundle_1.7.0.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.appengine.swarm_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.appsmarketplace_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.core_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer_2.6.0.r42x201206111227.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.UiBinder_2.6.0.r42x201206111227.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted.2_0_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted.2_0.super_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted.2_0.webkit_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted.2_0.webkit_win32x64_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.designer.hosted.2_2.webkit_2.6.0.r42x201206111222.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.login_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gdt.eclipse.managedapis_3.0.1.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/com.google.gwt.eclipse.sdkbundle_2.4.0.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/features/com.google.gwt.eclipse.sdkbundle.e42.feature_2.4.0.v201206290132-rel-r42.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/plugins/org.eclipse.wb.css_1.5.0.r42x201206111208.jar > . > Read timed out > Unable to read repository at > http://dl.google.com/eclipse/plugin/core/4.2/features/org.eclipse.wb.css.feature_1.5.0.r42x201206111208.jar > . > Read timed out > > -- > 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/-/FFTK69w1HwAJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Differentiated service with Google App Engine
Thanks David, I have stared the issue. On Fri, Jul 27, 2012 at 5:19 AM, David Hardwick < david.hardw...@bettercloud.com> wrote: > Hi > > If you put in a feature request to have two+ apps access the same > datastore natively then I will definitely star it! > > > On Thursday, July 26, 2012 3:11:48 PM UTC-4, rerngvit yanggratoke wrote: > >> Hello, >>Anyone have an idea on how to achieve a differentiated service >> with Google App Engine? I have two types of users. One is premium while >> another one is free user. I would like to set different minimum latencies >> for firing up new GAE instances between the two. In other words, I am >> willing to pay extra for the traffic generated from the premium users. >> Nonetheless, for the free users, I would prefer to pay at minimum or within >> the daily free quota provided by Google. In my case, I expect that the free >> users are able to tolerate higher latency than the premium ones. I believe >> that this case should be quite general and apply to many people. >>Assuming that I can identify types of users by the URLs they use >> or via other mechanisms. The only way I could think of is creating two >> separated applications and letting the premium users access the one that >> enables billing, while free users access the one that doesn't. However, my >> free and premium users need to share the datastore because they are also >> have to communicate within the application. Unfortunately, it seems that >> sharing a datastore across applications is not possible at the moment (feel >> free to correct me if I am wrong). >> >> Any ideas or suggestions? >> >> Cheers, >> Rerngvit >> > -- > 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/-/-mTVi29GpDwJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Differentiated service with Google App Engine
Thanks, Drake. I believe that surely will help with the prioritization of CPU resources. It's only that I am more concerned with the cost of running extra GAE instances because that is the major cost at the moment. On Fri, Jul 27, 2012 at 5:41 AM, Drake wrote: > If you are on a mult-threaded platform… you can achieve this by just > adding a Wait to the people you want to run slower. That will free CPU for > the other request. > > ** ** > > When you go over 8 requests per instance this will have less effect, but > generally how it works is > > User 1 Process start: > > User 1 runs until you hit an API > > User 2 Starts: > > User 2 runs until you hit an API > > User 1 Resumes: > > User 1 runs until an API > > User 2 resumes: > > User 2 runs until an API > > User 1 finishes > > User 2 finishes > > ** ** > > If you insert Pause/wait/DoNothing Spacers in your code that are > condition on the QoS of the user then the non-delayed user will get > priority. > I do a similar trick to make certain that low priority requests don’t > cause high priority requests that are near the timelimit from finishing.** > ** > > ** ** > > Better to know that you can serve 100 small tasks and only hit 75% CPU > than to have a big task drop because small tasks ate all the CPU. > > ** ** > > *From:* google-appengine@googlegroups.com [mailto: > google-appengine@googlegroups.com] *On Behalf Of *David Hardwick > *Sent:* Thursday, July 26, 2012 8:17 PM > *To:* google-appengine@googlegroups.com > *Subject:* [google-appengine] Re: Differentiated service with Google App > Engine > > ** ** > > If you put in a feature request to have more than one app access the same > datastore natively, then I will surely start that issue! > > On Thursday, July 26, 2012 3:11:48 PM UTC-4, rerngvit yanggratoke wrote:** > ** > > Hello, > >Anyone have an idea on how to achieve a differentiated service with > Google App Engine? I have two types of users. One is premium while another > one is free user. I would like to set different minimum latencies for > firing up new GAE instances between the two. In other words, I am willing > to pay extra for the traffic generated from the premium users. Nonetheless, > for the free users, I would prefer to pay at minimum or within the daily > free quota provided by Google. In my case, I expect that the free users are > able to tolerate higher latency than the premium ones. I believe that this > case should be quite general and apply to many people. > >Assuming that I can identify types of users by the URLs they use or > via other mechanisms. The only way I could think of is creating two > separated applications and letting the premium users access the one that > enables billing, while free users access the one that doesn't. However, my > free and premium users need to share the datastore because they are also > have to communicate within the application. Unfortunately, it seems that > sharing a datastore across applications is not possible at the moment (feel > free to correct me if I am wrong). > > ** ** > > Any ideas or suggestions? > > ** ** > > Cheers, > > Rerngvit > > -- > 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/-/cs1aYijZARwJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Differentiated service with Google App Engine
However, sharing datastore across applications is one of the solutions to the differentiated service. I am happy with GAE team comes up with other solutions as well. As a result I created a new issue specifically to this. Anyone who need this are welcome to star the issue. http://code.google.com/p/googleappengine/issues/detail?id=7901&thanks=7901&ts=1343371922 On Fri, Jul 27, 2012 at 6:39 AM, Kyle Finley wrote: > David and anyone else who is interested here's the feature request: > http://code.google.com/p/googleappengine/issues/detail?id=1300 > > Instead of allowing multiple apps to share one datastore; It appears that > the App Engine team is planning on giving more control over app versions, > in the future. I believe this is the Google IO session that discusses it: > > http://www.youtube.com/watch?v=zQ5_47zy4bY > > > -Kyle > > On Thursday, July 26, 2012 10:19:12 PM UTC-5, David Hardwick wrote: >> >> Hi >> >> If you put in a feature request to have two+ apps access the same >> datastore natively then I will definitely star it! >> >> >> On Thursday, July 26, 2012 3:11:48 PM UTC-4, rerngvit yanggratoke wrote: >>> >>> Hello, >>>Anyone have an idea on how to achieve a differentiated service >>> with Google App Engine? I have two types of users. One is premium while >>> another one is free user. I would like to set different minimum latencies >>> for firing up new GAE instances between the two. In other words, I am >>> willing to pay extra for the traffic generated from the premium users. >>> Nonetheless, for the free users, I would prefer to pay at minimum or within >>> the daily free quota provided by Google. In my case, I expect that the free >>> users are able to tolerate higher latency than the premium ones. I believe >>> that this case should be quite general and apply to many people. >>>Assuming that I can identify types of users by the URLs they use >>> or via other mechanisms. The only way I could think of is creating two >>> separated applications and letting the premium users access the one that >>> enables billing, while free users access the one that doesn't. However, my >>> free and premium users need to share the datastore because they are also >>> have to communicate within the application. Unfortunately, it seems that >>> sharing a datastore across applications is not possible at the moment (feel >>> free to correct me if I am wrong). >>> >>> Any ideas or suggestions? >>> >>> Cheers, >>> Rerngvit >>> >> -- > 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/-/F8SZuWOop_EJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Instances/Java go crazy
Just try with my app in Java runtime and do not find the problem. Which runtime you are using? On Mon, Jul 30, 2012 at 5:47 PM, Mos wrote: > Anyone else seeing issue with GAE instance management? > In one minute - 10 requests - around 5 instances are started. Old ones > do not response. New instances are created again and again... > > http://code.google.com/p/googleappengine/issues/detail?id=7910 > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] How can I block curl requests
I think you can blacklist those IPs. Have a look in https://developers.google.com/appengine/docs/java/config/dos#About_dos_xmlor https://developers.google.com/appengine/docs/python/config/dos. On Wed, Aug 1, 2012 at 10:43 PM, Kate wrote: > I am getting tens of thousands of curl requests - many thousands time > browser requests and I want to block them. I'm using python. They coming > from many different IPs most in Europe. If I can't stop them I will have > to close my site or go to a new provider. > > Thank in advance, > > Kate > > > > > > > -- > 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/-/L7wDtd5rrUcJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: What are the pros and cons of using Google App engine for my startup?
ved this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: What are the pros and cons of using Google App engine for my startup?
Hello Drake, That is possible but would increase your application size. Then, why not use JDO or JPA instead? It is the same lines of reason. On Sat, Aug 4, 2012 at 11:13 AM, Drake wrote: > If you have lockin you are doing it wrong. > > Wrap your Google Specific API calls so that they function like the Heavy > versions you can’t/shouldn’t use. > > ** ** > > *From:* google-appengine@googlegroups.com [mailto: > google-appengine@googlegroups.com] *On Behalf Of *Rerngvit Yanggratoke > *Sent:* Saturday, August 04, 2012 1:49 AM > *To:* google-appengine@googlegroups.com > *Subject:* Re: [google-appengine] Re: What are the pros and cons of using > Google App engine for my startup? > > ** ** > > As many people have stated about advantages of GAE for startup already, > let me provide some disadvantages. The purpose of this is not to discourage > people to use GAE but inform them about both sides of the story. > > ** ** > > The first and most important issue is a vendor lock-in. GAE normally > requires you to spend significant efforts to develop and optimize > specifically for the platform to run your applications nicely and cost > effectively. For example, it is recommended to use a platform-specific > database layer like Objectify than the portable but heavy-weight one like > JPA or JDO. Another example is that it is recommended to minimize the size > of your applications to reduce the cold-start time. This also means that > very useful but heavy-weight frameworks like Spring are not going to be > comfortable with GAE unless you are willing to pay a steep price of > "reserved instances". As a result, if one day you have to move your > applications away from GAE to somewhere else, porting your applications is > not going to be an easy task. You might have to spend significant resources > for that. The possible reason for the movement might be that Google > increases the price significantly such that your business model is not > sustainable anymore. This happened before to many people. Have a look in > the highly popular forum topic ( > https://groups.google.com/forum/?fromgroups#!topic/google-appengine/obfGjbIkOTI). > Now, some people might argue by bringing up Opensource alternative of GAE > like Typhoonae (http://code.google.com/p/typhoonae/) or AppScale( > http://code.google.com/p/appscale/). Despite the fact those are great and > honorable attempts, neither of them are fully compatible with GAE. In other > words, if your applications run smoothly on GAE, they might simply break > apart on their platforms. > > ** ** > > The second issue is the development efforts and learning curve required. > GAE is designed for highly scalable applications and require you as a > programmer to think the same. It certainly requires a new mindset compared > to a traditional web applications development. Generally speaking, > everything you do should be able to implement in a fully distributed way. > For instance, you should not use a relational database like Mysql because > it is a major bottleneck in traditional web applications. (You actually can > use it now with Google Cloud SQL. However, it deteriorates the purpose of > running an application for GAE). > > ** ** > > The third issue is a sharing of fate. This is actually not just for GAE > but for any other cloud solutions. You are going to run your applications > on a shared infrastructure. You do not know what applications are run > besides you in the same IP. They might be spam or malicious software > developed by hackers. Then, the IP might be blocked for a security reason. > An example of this is the recent CloudFlare blocking issue ( > https://groups.google.com/forum/#!msg/google-appengine/Q6yQ4d9ov-o/hAyrgn0xZQwJ > ). > > ** ** > > All in all, the major thing to concern is picking the right tool for the > right job. GAE is suitable if your applications require a very high > scalability and you don't have or want to operate an operation team (System > administrators). Other than that, I would recommend you to find other > options. > > ** ** > > On Sat, Aug 4, 2012 at 1:03 AM, hyperflame wrote:** > ** > > It would be a good fit for most of those subjects, but keep in mind > that GAE cannot access email through IMAP or POP3 because it doesn't > support sockets, only standard url fetch. If you want to include email > in your service, you'll have to base a proxy somewhere else, such as > Rackspace, Heroku/AWS, etc. > > > On Aug 3, 4:37 am, Levi Campbell wrote: > > I'm building a startup, and I'm considering GAE as the platform, however > > I've been having a hard time finding information on why a startu
Re: [google-appengine] Loading time
Another random guess. Is it from the cold start time? 5-10 seconds is only for the first time or it's true also for the subsequent requests? On Sun, Aug 12, 2012 at 6:52 PM, Nico wrote: > Hi, i have been running some tests (in java), my app just goes to the DB > and shows some info. My question is: Why when i load the site it lasts like > 5-10 seconds to load completely? Mostly having in mind that the code does > almost nothing. > > http://matchreminder.appspot.com/matchreminder > > Any idea? > Thanks in advance! > > -- > 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/-/f1-Iyb20RBEJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Why GAE request takes so much time?
You can use Appstat to profile your application. Have a look at http://googleappengine.blogspot.com/2010/03/easy-performance-profiling-with.html . On Mon, Aug 13, 2012 at 11:19 AM, ailinykh wrote: > Hello, everybody! > I have simple GWT application which is running against GAE. > The problem is - simple query takes too long. I put log result below. As > you can see it takes almost 4 seconds (this is not first request which > causes a new process started). I added logging into my data access class > (RawData). > It shows that all data reading takes only 29 ms. So, my question is - who > consumes rest of cpu? How can I profile my application to get clear picture? > > Thank you, > Andrey > > > 2012-08-12 20:48:16.781 /gwtRequest 200 3918ms 87kb Mozilla/5.0 (X11; > Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.168 > Safari/535.19 > 98.210.16.181 - - [12/Aug/2012:20:48:16 -0700] "POST /gwtRequest HTTP/1.1" > 200 87656 "http://hikeinthecloud.appspot.com/"; "Mozilla/5.0 (X11; Linux > x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.168 > Safari/535.19" "myapp.appspot.com" ms=3918 cpu_ms=3028 api_cpu_ms=39 > cpm_usd=0.093998 instance=00c61b117cd5d51838dc0c430d3d0123c842a9 > I 2012-08-12 20:48:12.905 > domain.RawData getData: getData 1344719667, 1344725313 > I 2012-08-12 20:48:12.907 > domain.RawData getData: Start getting data... > I 2012-08-12 20:48:12.908 > domain.RawData getData: Finish getting data. 1ms > I 2012-08-12 20:48:12.936 > domain.RawData getData: Return data. 2 backets, 29ms > > -- > 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/-/9AL-Q8TR_9kJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Loading time
Have you try profiling your app with Appstat( http://googleappengine.blogspot.com/2010/03/easy-performance-profiling-with.html )? On Wed, Aug 15, 2012 at 3:50 AM, Nico wrote: > It takes 5-10 segs to load the test servlet. > > PseudoCode: > Creates 1 PersistanceManager instance. > Creates and makes persistent like 11 entities. > Brings entities back by id and shows them. > > I have no problem uploading the code, but i think that the description > above is basically all the test does. > > Thanks! > > -- > 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/-/alUwPukknOEJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Google App engine read quota exceeded suddenly
>From what I understand, the memcache service is not reliable. In particular, it is not guaranteed that the data you store will be persistent forever. Your code have to handle that case. This is a typical usage of "cache" anyway. :) Regarding the limit, it is 1MB per entry as can be seen from here ( http://stackoverflow.com/questions/5081502/memcache-1-mb-limit-in-google-app-engine ). On Wed, Aug 22, 2012 at 12:18 AM, Piyush Grover wrote: > I have a google app engine connected with an android app. People add and > read updates to it which gets stored in the app engine datastore. I am > using memcache in a proper way and on an average my last month read > operations were not more than 25%. One day within a span of 6 hours the > quota reached to 100% and when I looked at the statistics of data read, it > was almost the same as in previous days. When I looked at it, I found that > my memcache had nothing in it. > How the memcache suddenly lost its data? > Is there any limit on the memcache size? > > -- > 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/-/Bzl2Qu4-Vr8J. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Google App engine read quota exceeded suddenly
On Thu, Aug 23, 2012 at 12:20 AM, Joshua Woodward wrote: > On Wed, Aug 22, 2012 at 10:14 AM, Rerngvit Yanggratoke > wrote: > >> From what I understand, the memcache service is not reliable. In >> particular, it is not guaranteed that the data you store will be persistent >> forever. > > > What do you mean by "not reliable"? > > I hope you mean the memcache service itself is reliable, however don't > rely on your data being available to you when you go back to fetch it. > That's what I mean, thanks. The OP asked "How the memcache suddenly lost its data?". I explain that it doesn't lose but it works this way. > I don't know of anything that stores permanently in memory, on any system. > > > > >> Your code have to handle that case. This is a typical usage of "cache" >> anyway. :) >> >> Regarding the limit, it is 1MB per entry as can be seen from here ( >> http://stackoverflow.com/questions/5081502/memcache-1-mb-limit-in-google-app-engine >> ). >> >> On Wed, Aug 22, 2012 at 12:18 AM, Piyush Grover < >> piyush4u.iit...@gmail.com> wrote: >> >>> I have a google app engine connected with an android app. People add and >>> read updates to it which gets stored in the app engine datastore. I am >>> using memcache in a proper way and on an average my last month read >>> operations were not more than 25%. One day within a span of 6 hours the >>> quota reached to 100% and when I looked at the statistics of data read, it >>> was almost the same as in previous days. When I looked at it, I found that >>> my memcache had nothing in it. >>> How the memcache suddenly lost its data? >>> Is there any limit on the memcache size? >>> >>> -- >>> 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/-/Bzl2Qu4-Vr8J. >>> To post to this group, send email to google-appengine@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >>> >>> >> >> >> -- >> Best Regards, >> Rerngvit Yanggratoke >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > > > -- > > > > Google+ - http://joshuawoodward.com/+ > Twitter - @howtohtml5 <http://twitter.com/howtohtml5> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Creating a game on app engine - calculating costs, thoughts?
I'm also looking into a similar problem. You can use Channel API to avoid
polling and thus unnecessary datastore operations. However, Channel API
also has limited free quota.
On Fri, Aug 24, 2012 at 5:37 AM, Mark wrote:
> Hi,
>
> I'm trying to see if it's feasible to write a game using app engine as the
> backend.
>
> The task I'm most worried about is the discoverability of games. A user
> can create a new game (which creates a Game object in the datastore). Then
> other users can hit an endpoint to get a listing of open games, sorted by
> creation date.
>
> Creating a new game will be a very low frequency operation, so no worries
> there. Users polling for new open games will be much higher in frequency
> though. Each time a user requests a listing of games, I need to go fetch a
> page of Game objects from the datastore. Let's say a page size = 20. And
> the Game object looks like this:
>
> class Game {
> String name;
> long timestampCreated;
> long timestampStarted;
> String mapName;
> String hostUsername;
> int numPlayersMax;
> List playerNames; // usernames of other players currently
> joined
> Text gameState; // game state as serialized json string
> }
>
> the query would be something like:
>
> select Games where timestampStarted = 0
> and playerNames.size() < numPlayersMax
> order by timestampCreated DESC limit 20;
>
> First, I'm hoping it's possible to avoid loading the Text field in this
> listings query since it's not needed for rendering yet. Still there would
> be a fair number of fields to fetch and deserialize, and I'm afraid my
> costs would quickly make it impractical.
>
> I could try keeping a list of open games in memcache, but not sure if I
> could achieve consistency between the memcache state and the datastore
> state of games. Will be looking into that.
>
> I've got a very similar game to this already published, using a single
> jetty instance + mysql on one machine. It's starting to get too much
> traffic now, and scaling would be a pain. App engine's scalability looks
> great for something like this, but not sure if the # of writes and
> inefficient reads I need to perform are a good idea.
>
> Any general thoughts on this would be greatly appreciated. I'm starting to
> dig into this now and any thoughts on how you'd implement the above would
> be great. In my already-published game (mentioned above), I ran a dark test
> where I'd call through to a (quickly implemented) mirror of the game
> running on app engine. It quickly ate through the daily quota!
>
> Thanks
>
> --
> 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/-/cvpOxGrMRaoJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
--
Best Regards,
Rerngvit Yanggratoke
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Nearest match in the database
Store n-gram indexes and search by that (http://en.wikipedia.org/wiki/N-gram). You probably have to limit n to small numbers (ex. 5) to reduce database size. On Fri, Aug 31, 2012 at 11:18 PM, Sadaf Noor wrote: > Hello, > > How can i retrieve nearest match from a database? > > Suppose, I have a table which has different names ["", > "","",""]. When I will query for a name like "aa" it should > return "". Is there any way to do that? Or any other suggestion to that? > > -- > > Regards, > > *Md. Sadaf Noor,* > > ID:11121023, > Electrical and Electronic > Engineering<http://www.bracu.ac.bd/academics/dept/course.php?code=BSEEE> > , > BRAC University <http://www.bracu.ac.bd>. > > Contact: > Email:sadafn...@acm.org > > sadafn...@ieee.org > Mobile: +8801758085078 > Website: sadaf2605.appspot.com > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Best Regards, Rerngvit Yanggratoke -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
