[google-appengine] Re: Is Google killing GAE?

Don't agree, I don't see the evidence to support you claims. I think it has probably been more successfull than they can afford and need to start re-couping the massive cost of running such an service. But thats my opinion, only google can really tell us the truth of the matter. I will leave i

[google-appengine] Re: Is Google killing GAE?

I dont think Google want to kill GAE at this moment. However I would say they have given up growing of the platform anymore. As I said in another thread, if GAE hasn't take off in the past 3 years, I dont see how it would under the new pricing model. A platform without user base just die by t

Re: [google-appengine] Re: SDK Upgrade 1.5.2: --datastore_path ignored?

Because they searched the groups and passed the default_partion argument to the dev appserver. On Sep 3, 2011 6:28 PM, "dop" wrote: > > I'm just amazed how little noise is there because of this issue. If I > understand it correctly after upgrading to 1.5.2 evenybody's local > datastore becomes e

[google-appengine] Re: Is Google killing GAE?

3 years is not a slow kill. Thats like saying Canonical is deprecating ubuntu because Long Term Support (*LTS*) version you get 3 years committed support. What the 3 years statment provides is organisations a committment they can rely on, which was never there whilst appengine is in preview.

[google-appengine] Re: Is Google killing GAE?

One example that the cloud providers have massive profit margins at the moment is an interview I watched where a CEO for a tech company said that they had moved from using Amazon cloud services (or some provider like that) to running their own data centers. And they cut their cost by an order of

[google-appengine] Re: Is Google killing GAE?

3 years is what I meant by a slow kill. But I hope my speculation is wrong. Cloud services is a very young market. Compare with for example a company selling consumer electronics. Such company will have a tiny profit margin because the market is so mature. In cloud computing on the other hand, t

[google-appengine] Re: Is Google killing GAE?

3 years is what I meant by a slow kill. But I hope my speculation is wrong. Cloud services is a very young market. Compare with for example a company selling consumer electronics. Such company will have a tiny profit margin because the market is so mature. In cloud computing however, the cloud

RE: [google-appengine] Re: Google Bot Is Your Enemy

Returning a 503 is REALLY REALLY Bad for SEO. 304 Seems to be ignored by Google Bot on GAE, but also Google Bot will try queries to which there are no links, and which no user has ever made. If your latency goes higher Google Bot will throttle back. but the only way to slow down the page s

Re: [google-appengine] The Amazing Story Of Appengine And The Two Orders Of Magnitude

+1 On 4 September 2011 03:51, Joshua Smith wrote: > Yes, that certainly seems possible.  But it's a lot more trouble than just > having a way to say to the scheduler, "run these when you have an idle > instance with nothing better to do," or "DO NOT spin up an instance just to > handle this ta

Re: [google-appengine] The Amazing Story Of Appengine And The Two Orders Of Magnitude

On 4 September 2011 01:35, Joshua Smith wrote: > I also identified task queues as the source of my excessive instances.  I > suspect this is a quite common issue, and together with datastore access bugs > (sorry, but you never should have written it like that) I totally agree with you! I don't

[google-appengine] Re: frontend instance specs

Especially once python 2.7 support is finally here... CPU will matter more than latency at that point from what I understand. -- 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.c

[google-appengine] Re: Is Google killing GAE?

This is all just nonsense, they are changing their business model. They wouldn't be taking appengine out of preview and then legally committing to the platform for 3 years if they where going to can. -- You received this message because you are subscribed to the Google Groups "Google App Engi

[google-appengine] Re: frontend instance specs

It matters even more now than before to make sure that one instance can handle as much as it possibly can. On Sep 3, 11:14 pm, Gopal Patel wrote: > 1.2Ghz is not our app runs on. That's reference point to calculate cpu > charge. i.e. if a 3.6Ghz server take 300ms to response, it will be charged

[google-appengine] Re: Is Google killing GAE?

Whoa! I just found out that App Engine for Business is closed. See: http://code.google.com/appengine/business/ But they will move that service into ordinary App Engine, including SQL support. So hopefully Google will continue to run and develop App Engine. And drop the horrible price on fronten

Re: [google-appengine] frontend instance specs

1.2Ghz is not our app runs on. That's reference point to calculate cpu charge. i.e. if a 3.6Ghz server take 300ms to response, it will be charged as 900ms. but thats history now, no more cpu. only instance time. On Sun, Sep 4, 2011 at 8:20 AM, Raymond C. wrote: > As far as I can remember, I dont

[google-appengine] Re: how many datastore api calls would happen in one datastore function call?

thanks. dose put() for add new or for edit take same ops? to edit may alter the property indexed or not indexed. if the entity has 2 indexes, one put() will take 5 ops in sum, right? how many will i save in using the keys_only than fetching the entity? On 9月4日, 上午3时30分, Philip wrote: > You ha

[google-appengine] Re: Google Bot Is Your Enemy

how about desallow googlebot in robots.txt or in code? googlebot is my biggest access source too. On 9月4日, 上午9时50分, johnP wrote: > I think in webmaster tools you can change crawl-rate preferences. > Otherwise - just block it with robots.txt. > > On Sep 3, 12:35 pm, "Brandon Wirtz" wrote: > > >

[google-appengine] Re: Is Google killing GAE?

There was a theory that GAE was started using Google's own infra-structure so they can absorb startups who run on GAE easily. E.g. Think about if twitter was started on GAE, if they dont enough revenue to keep running it, Google can take it and make its own service without any technical transi

Re: [google-appengine] frontend instance specs

As far as I can remember, I dont think we have seen the CPU spec neither. 1.2 GHz CPU is used for calculate the CPU time we consumed in the old pricing model. Back in the day we dont (need to) care how fast the CPU runs. -- You received this message because you are subscribed to the Google G

[google-appengine] Re: Google Bot Is Your Enemy

I think in webmaster tools you can change crawl-rate preferences. Otherwise - just block it with robots.txt. On Sep 3, 12:35 pm, "Brandon Wirtz" wrote: > The biggest Problem I have with the Scheduler/GAE isn't GAE it is Google > Bot. > > Under the new model you are on the hook for 15 minutes of

Re: [google-appengine] Re: Google Bot Is Your Enemy

@Brandon : This is the case for one of my popular web-sites too. I believe if latency time increases, Google bot will automatically scale down its crawl rate and I also fear that such an increased latency will have a negative effect on the page ranking. By the way, have you started using 304 (Not

Re: [google-appengine] Re: Should Google deprecate Master/Slave data store option?

The entity id (or name) is known / available after a put(). Fred on my Android. On Sep 3, 2011 2:47 AM, "NM" wrote: > In case of a wizard based interface with multiple steps where users > provide data at every step we have to ensure that we work off session > data. By and large we can conclude th

Re: [google-appengine] Re: Should Google deprecate Master/Slave data store option?

For the wizard, using an entity group will give you strong consistency. Use ancestor query or plain old fetch (get) by key to get strongly consistent results. In general, query public data using regular (eventually consistent) queries. Merge in the user's own, just committed, data. Most of the ti

[google-appengine] The 15 Minute Question?

Just how long does it take to fire up a brand new instance? And, did anyone explain why they are kept spinning for 15 minutes after any activity? Why is number of idle instances not used to determine how fast they are brought down? Finally, why are internal app processes started and stopped as n

Re: [google-appengine] Trying to get idle instances to 0

Interestingly prior to the new scheduler changes you could always get instances to disappear (the good ol' days ;-) Maybe moving forward we don't always get better ;-) T -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discuss

Re: [google-appengine] Trying to get idle instances to 0

FYI, A similar feature request was filled there: http://code.google.com/p/googleappengine/issues/detail?id=5764 On Sun,

[google-appengine] Trying to get idle instances to 0

Hi I have an unbilled HR app in development, that isn't being used much (say one request about every few hours), and it seems to sit for hours with a single instance idle for very long times, Total number of instancesAverage QPS*Average Latency*Average Memory1 total 0.000Unknown ms43.0 MBytes*

Re: [google-appengine] Dashboard graphs require instance hours graph

Hi I have been thinking further about what I think the bare minimum the graphs should be showing. It really needs instance hours cost on 15 min increments (or less) or if that is not possible at least instance hours, number of instances isn't the metric we are going to be charged on. For bur

[google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

Oh this is all nonsense. You are all smart enough to understand how it works. Google has dropped the ball, not providing appropriate real time tools to monitor instance hours and what it will cost you. You can also argue about the level of pricing, but to suggest it is any more complicated

[google-appengine] Re: I remember I ever read somewhere in gae documents, which says google internal apps also run on app engine

+1 Geoffrey This is way to much vitriol rather than constructive dialogue in this group at the moment. T -- 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-app

[google-appengine] Re: Is Google killing GAE?

recently. google closed many projects. Hope gae is not the next. In fact, after more than one year development on it, I really like gae in many aspects. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web vi

[google-appengine] Re: Why app engine new price model is totally wrong

Yes, I need. But this should NOT be reason for why gae computing charge 10 times than competitors. If it should, then the surroundings should not charge any more. On Sep 4, 6:39 am, Francois Masurel wrote: > Hi Tapir, > > If you don't need the surroundings, GAE is probably not be the right > solu

[google-appengine] Re: Why app engine new price model is totally wrong

Hi Tapir, If you don't need the surroundings, GAE is probably not be the right solution for you. Francois -- 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-ap

[google-appengine] Re: Why app engine new price model is totally wrong

"A GAE instance is much more than a 'slice of cpu and memory' - it has a whole 'platform' surrounding it. " yes, but the surroundings will cost extra money! On Sep 4, 6:14 am, Barry Hunter wrote: > Mainly because GAE is not a 'computing' platform as such. If want raw > computing power then again

[google-appengine] Re: SDK Upgrade 1.5.2: --datastore_path ignored?

I'm just amazed how little noise is there because of this issue. If I understand it correctly after upgrading to 1.5.2 evenybody's local datastore becomes empty. Yet very few seem to care. Weird... -- You received this message because you are subscribed to the Google Groups "Google App Engine" g

[google-appengine] I need ask it again, for I didn't get a direct answer from googlers. Why gae computing price is so high.

Please don't talk about others such storage, just for the computing. Please the first post in this thread: http://groups.google.com/group/google-appengine/browse_thread/thread/4a42af11f488f9f0 Specially, here I compare your B! backend and amazon Small Instance. B1 128MB 600MHz $0.08 per

[google-appengine] Re: Is Google killing GAE?

Often even generally well-informed customers are fooled by pricing models. One example is the failure to take into account the exponential progress of price/performance. The customers are happy when the price doesn't go up year after year. What they miss is that the actual cost for computing pow

Re: [google-appengine] Re: Why app engine new price model is totally wrong

Mainly because GAE is not a 'computing' platform as such. If want raw computing power then again elsewhere will probably suit you better (and save some money) A GAE instance is much more than a 'slice of cpu and memory' - it has a whole 'platform' surrounding it. Apples != Oranges again. Or to p

[google-appengine] Re: Why app engine new price model is totally wrong

I have started a new thread about a possible reason for the higher prices: http://code.google.com/appengine/forum/?place=topic%2Fgoogle-appengine%2F6WqUi10P8Yo%2Fdiscussion Just a speculation, but you can check it out in case it has some truth to it. -- You received this message because you ar

[google-appengine] Re: Why app engine new price model is totally wrong

"Ok, sorry about that. But one thing to remember is that SQL is much more ..." hi, Anders, again, this thread is to compare computing prices, not data storage. You will pay extra data storage money when using gae. I just want to get a reason from googlers why gae computing cost 10 times than compe

[google-appengine] Re: I remember I ever read somewhere in gae documents, which says google internal apps also run on app engine

On Friday, September 2, 2011 5:35:18 PM UTC-4, Tapir wrote: > > I just want to say, if it is true, with the new gae price model, you > google will go bankrupt. > Now you're just trolling. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group

[google-appengine] How can I request an alias for my application?

Hi, I have two questions: 1) The title of this thread: How can I request an alias for my application? 2) And how long does it take? Ernesto -- 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://

Re: [google-appengine] Idle instances for free apps

That's what I was assuming. Thanks for the reply. -- 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/-/KkhSasgCvS0J. To post to this group, send email t

[google-appengine] Re: Google Bot Is Your Enemy

Nice, so basically Google is using their own service to tack on additional charges to your bill. Doesn't sound ethical. -- 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.

[google-appengine] Re: Is Google killing GAE?

And at the same time Google is making a statement by setting a price on instances to show how other cloud providers are totally ripping off their customers by doing so. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussi

Re: [google-appengine] Idle instances for free apps

Hi Stephen, For free apps you can't set min idle instances for free apps (which is similar to always-on) but you will periodically have idle instances after they have finished a task or being spun up in response to a load. Greg On Sat, Sep 3, 2011 at 9:08 PM, stephenp wrote: > I'm guessing tha

[google-appengine] Idle instances for free apps

I'm guessing that low-traffic free apps won't be able to have any idle instances in the post-preview appengine world. Is that correct? It sounds like you have to turn billing on to be able to tell the scheduler you want 1 idle instances. Correct? Thanks, Stephen -- You received this message

[google-appengine] Is Google killing GAE?

I have started to suspect that Google on purpose is killing GAE. Because they know by now that they will not get enough large customers. See for example this article: http://blog.labslice.com/2010/12/2010-cloud-computing-winner.html which shows that GAE has a very tiny market share. I think the

[google-appengine] Re: GAE pricing is not suited for smaller apps

It depends on what you mean by small. Many apps will still be able to run for free on GAE. But yeah, as soon as an app goes beyond the free quotas then the pricing may be way too high. And companies developing larger applications may not want to use GAE because of the limited datastore function

Re: [google-appengine] Google Bot Is Your Enemy

Is there some way to get google bot requests to go to a dedicated back end? On Sep 3, 2011, at 3:35 PM, Brandon Wirtz wrote: > The biggest Problem I have with the Scheduler/GAE isn’t GAE it is Google Bot. > > Under the new model you are on the hook for 15 minutes of time for an > instance that

Re: [google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

This point is not so simple: > (and unfortunately may remain > that way because instance optimization is markedly revenue and profit > negative for GAE) It really is not in google's economic interest to have idle instances running. More idle instances means more infrastructure cost, and, if you

Re: [google-appengine] frontend instance specs

Hi, Can you point us to where you got this from or how you figured this out? I can see the 128MB (I used a sample app to figure out when App Engine starts throwing OutOfMemoryErrors), but where did you get the 1.2 GHz CPU from? Is there a document somewhere you can point to, or did you decipher

Re: [google-appengine] Re: Porting App Engine app to other provider - ideas and discussion

Although a lot of us are upset about how this was handled, I'd suggest testing how much you can optimize first. If that doesn't help, I have a couple of suggestions below. Here is my own plan: 1. Start with optimizing settings. Things like reducing max idle instances and lowering the rate on low p

[google-appengine] Re: GAE pricing is not suited for smaller apps

+1 re: scheduler. The ironic thing to me is that when we got the lead-time announcement in May, the wails of discontent were calmed by GAE engineers in these boards citing how we should wait the see the affect Scheduler would have. Google PR is obviously busy these days suggesting that the current

[google-appengine] Google Bot Is Your Enemy

The biggest Problem I have with the Scheduler/GAE isn't GAE it is Google Bot. Under the new model you are on the hook for 15 minutes of time for an instance that spins up. Google Bot can't be throttled on GAE. If you go in to WebMasters Tools you get a "Your site has been assigned a special c

[google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

Totally agree. New billing is too complicated to control and too expensive when you don't do it. Old billing wasn't and it's low cost in absolute wash't the reason. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion o

[google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

I had spent most of the night wondering about task queue's apparent inefficiencies under Scheduler, and had planned to open a topic related to it, but then read Joshua's post. THIS point made by Joshua is THE HEART of the issue:'...it's a lot more trouble than just having a way to say to the sched

[google-appengine] Re: how many datastore api calls would happen in one datastore function call?

You have to consider the following points: - put() Each property the entity has will add at least 2 extra write ops if the property is indexed (for asc and desc order) - fetch() Don't use the offset property; you will be charged for (number_of_items + offset) read ops. If you need paging you have

Re: [google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

+111 Totally agree. There should be simplified billing process. On Sat, Sep 3, 2011 at 11:49 PM, Arun Shanker Prasad < arunshankerpra...@gmail.com> wrote: > +1 > > absolutely agree, may be Google can put up an an article detailing > what this means to normal users? > > -- > You recei

Re: [google-appengine] The Amazing Story Of Appengine And The Two Orders Of Magnitude

THAT is a fantastic idea. -- 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/-/qa8mqxfJ25MJ. To post to this group, send email to google-appengine@goog

Re: [google-appengine] The Amazing Story Of Appengine And The Two Orders Of Magnitude

Yes, that certainly seems possible. But it's a lot more trouble than just having a way to say to the scheduler, "run these when you have an idle instance with nothing better to do," or "DO NOT spin up an instance just to handle this task" On Sep 3, 2011, at 12:14 PM, peterk wrote: > You can p

[google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

+1 absolutely agree, may be Google can put up an an article detailing what this means to normal users? -- 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 unsubscri

[google-appengine] Re: Strange Backend Behavior

Hey, thanks, that actually seemed to have helped. I still don't get any log messages, but I'm now using memcache to output some debug information into a handler running on the server, and it's actually deleting data. Thanks for the help! On 3 Sep., 17:32, Tim Hoffman wrote: > With this code you

Re: [google-appengine] frontend instance specs

Also, another indication that too many frontend instances are sharing the same physical server is that I have noticed that even with low traffic the scheduler usually starts many instances. What should easily be handled by one frontend instance is handled by a whole bunch of instances, and we as

Re: [google-appengine] frontend instance specs

Also, another indication that too many frontend instances are sharing the same physical server is that I have noticed that even with low traffic the scheduler usually starts many instances. What should easily be handled by one frontend instance is handled but a whole bunch of instances, and we a

Re: [google-appengine] frontend instance specs

1.2 Ghz Intel single core? What about time sharing? I suspect Google squeezes in a lot of instances in each physical server, so that with time sharing of the CPU the instances in reality get a lot less than that when the load is high, and judging by how often instances are swapped in and out o

[google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

I totally agree too. -- 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/-/UUEqYNKsmukJ. To post to this group, send email to google-appengine@googlegrou

Re: [google-appengine] frontend instance specs

dont know what we are using, but we are charged for 1.2Ghz intel single core. and 128MB Max before instance get killed. On Sat, Sep 3, 2011 at 9:50 PM, GR wrote: > What are the memory and CPU specs of the frontend instances we are paying > for? > > -- > You received this message because you are

[google-appengine] frontend instance specs

What are the memory and CPU specs of the frontend instances we are paying for? -- 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/-/BMlk7vkQkbEJ. To pos

Re: [google-appengine] Re: App Engine will not be leaving preview prior to Sept 26th

initially I misunderstood the maximum idle instances. it exactly means that. if your app set to 2 idle instance. your app will have as many instances as it needs. but if traffic reduces it will kill rest of the idle instance apart from last two AFTER their 15 minutes cycle over. so if there is a sm

[google-appengine] Re: The whole instances pricing thing is too complicated for average brains like mine

I completely agree. This is why the cpu time was a superior metric to instance hours. That way we had a reason to write efficient code and Google had every reason to write an efficient scheduler to not waste instance hours. -- You received this message because you are subscribed to the Google

[google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

You can pull from task queues instead of having them push, right? That could help a lot where task queues are the source of instance spin up. I'd even be happy to dedicated a back-end to task queue pull-work if it was necessary - at least that is totally under your control. On Sep 3, 5:05 pm, Jo

Re: [google-appengine] Re: The *real* cost of the new billing prices

It's not "without reason." The scheduler behaves quite predictably. Just look at the logs and find the requests that start up new instances. You'll see that they are bunched up with other requests. And there is a good chance they are coming from task queues. On Sep 3, 2011, at 12:05 PM, Nick

Re: [google-appengine] The Amazing Story Of Appengine And The Two Orders Of Magnitude

I also identified task queues as the source of my excessive instances. I suspect this is a quite common issue, and together with datastore access bugs (sorry, but you never should have written it like that) like the one you found, are conspiring to make a lot of these crazy new billing numbers.

[google-appengine] Re: The *real* cost of the new billing prices

If you can only keep it down to one instance, it will be free. You get 24 instance hours per day as part of the free quota. But god help you if you think you can keep it to one. The scheduler can and will at any time fire up additional instances seemingly without reason. -- You received this m

[google-appengine] Re: App Engine will not be leaving preview prior to Sept 26th

I agree this scheduler needs a lot of work. I also think Google should not be charging us based on a black box algorithm that we cannot directly control or understand. Any defect or problem in the scheduler will dramatically cost us when it should be Google that pays for any defects like that.

[google-appengine] Re: The scheduler needs a fix and quick.

This scheduler is quite the conflict of interest in that Google controls the algorithm and profits from any defects that cause us to have unnecessary instances running. Google, please go back to CPU based pricing or some metric that aligns both our interests - we should have incentive to write

[google-appengine] Re: Strange Backend Behavior

With this code you I think you won't be reclaiming any memory. You could try a gc.collect, in addition move the deletions in your code so that the deletes occurr in a function. I would have the outer loop use a cursor, pass the query to a function that does the fetch of the keys and does the de

[google-appengine] Does Account credit remain on the account if billing is disabled?

If I: 1. I have a credit on my account, E.g. ($50) 2. I disable billing. 3. 3 months latter I re-enable billing. Do I still have the credit? Thanks, - Kyle -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the

[google-appengine] Re: The *real* cost of the new billing prices

Hi Actually I believe I can get my price down below $30 a month, keeping a single instance running will cost around $30. I can get down to single instances no problems. Sure the scheduler isn't helping. Total number of instancesAverage QPS*Average Latency*Average Memory1 total 0.01761.0 ms49.9

[google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

Which leads to a potential constructive suggestion. Maybe Goog can post a troubleshooting guide that lists different line-items in the new-style billing, and potential gotchas? An example in your blog is that sudden parallelism is costly and that making things serial is a good optimization. (Ir

[google-appengine] How to Send Email in Google App Engine

Hi, I am new in Google app. i need to send email through java api. i am using mail.jar,smtp.jar. when i try to run . the following error is encounter. *java.net.Socket is a restricted class. Please see the Google App Engine developer's guide for * *more details.* But it runs in java applicat

[google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

Excellent information. This is very similar to my experience and I suspect explains most of the trouble with the new billing scheme. At least the datastore reads are very much within our control. As for keeping the instance count low, I still don't see that as very easy to do. I'd be very curio

[google-appengine] Re: how many datastore api calls would happen in one datastore function call?

how about these funtions? i use these. Model.put() .get() .fetch() .count() .gql() .all() On 9月3日, 下午10时08分, Philip wrote: > Provide some example code. > > On Sep 3, 3:53 pm, saintthor wrote: > > > > > > > > > today, till now, one of my apps get 1888 requests and 41090 datastore > > api

[google-appengine] Re: how many datastore api calls would happen in one datastore function call?

Provide some example code. On Sep 3, 3:53 pm, saintthor wrote: > today,  till now, one of my apps get 1888 requests and 41090 datastore > api calls. i think the api calls should not be so many. -- You received this message because you are subscribed to the Google Groups "Google App Engine" gro

[google-appengine] Re: Backend confusion

I've had the same issues with the backend logservice. As soon as I use logservice anywhere in the code, no log messages will appear at all, except for service error 201 and instance startups. I've also posted a related post here: http://groups.google.com/group/google-appengine/browse_thread/thread

[google-appengine] how many datastore api calls would happen in one datastore function call?

today, till now, one of my apps get 1888 requests and 41090 datastore api calls. i think the api calls should not be so many. -- 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@googlegroup

[google-appengine] Re: Porting App Engine app to other provider - ideas and discussion

Regarding hosting options, I am looking at rackspace since there are many successful businesses outside are using it. Now looking at if I should switch to node.js or keep running python on the new server. -- You received this message because you are subscribed to the Google Groups "Google App

[google-appengine] Re: The *real* cost of the new billing prices

Thanks so much for your reply. Congratulates you still find yourself fit in the new pricing model. Unfortunately I dont find it myself. The money I will be paying for under the new price allows me to rent several powerful servers on rackspace or EC2, just to serve 30-60 requests per second. (

[google-appengine] Re: Is billing usage reports running 3 days behind for everyone?

its the same. You have to implement changes, wait 3 days, implement new changes, wait 3 days... etc. You can get some idea of the change by looking at the instances spawned real-time. The graph is weird and doesnt really give you info. When a new instance is spawned it says so in the logs - so

[google-appengine] Porting App Engine app to other provider - ideas and discussion

Looking for suggestions and new ideas on how to port my App Engine app to another provider. I could deal with the datastore errors, 500 and timeouts. There were ways around this issue by caching better etc. However, the billing issue has forced me to realize that Google has decided to profit fr

[google-appengine] Strange Backend Behavior

Hey, we've accumulated a large dataset on our appengine (almost a terrabyte now), and we're struggling to delete it (mostly old data that is no longer needed). After years of trying this and that, I gave backends a shot, but the behavior is really strange. Essentially, I've got a little deleter

[google-appengine] Re: The *real* cost of the new billing prices

In your post you claim that everything will be okay (even though you jumped from 9USD to 30USD pr month = 420 USD pr year). The basis for this is that you say that you do not really need the 3 instances running - only 1. Thats all mighty fine - but the problem is that you can't get it down to on

[google-appengine] Re: The *real* cost of the new billing prices

Please note, I am not an apologist for the new billing regime, I think there have been some major misteps with it, especially with regards to clarity of information , lack of tools to really gauge the impact of your own chnages. Billing stats 3 days old is pretty useless if you trying to reduce

[google-appengine] Re: The *real* cost of the new billing prices

Hi Raymond Here you go, posted about it earlier today. This is at the low end of the equations and numbers talkd about around here. But appengine still works for me. https://groups.google.com/d/msg/google-appengine/0tKkjM5xlc4/1bmSJx5huvwJ Rgds T -- You received this message because you a

[google-appengine] Re: The Amazing Story Of Appengine And The Two Orders Of Magnitude

Very good read, thanks for posting. Will definitely be curious to see how your changes improve things or otherwise. On Sep 3, 11:16 am, Emlyn wrote: > Hi all, > > I don't think I've posted here before, but I've been an appengine user > for a while now (closing on 2 years? Is that even possible?

Re: [google-appengine] Some more real-world low-traffic scheduling data -- and a diagnosis

Someone else suggested that as well. I don't grok backends yet, so I don't know. But the fix I described in this message seems to have solved my issue: In fact, since I'm optimizing for the one-instance case, I actually just implemented a trivial cache. The first hit from the kiosk generate

[google-appengine] Re: The *real* cost of the new billing prices

Glad there is someone not. Tim, would you mind sharing your data on the price change? I mean the numbers that makes you still think GAE is a good platform for you to stay. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discu

[google-appengine] Re: The *real* cost of the new billing prices

Absolutely not. I don't regret a single thing I have said about appengine. I always explain the risks too. I have been here a long time, and been pretty vocal about shortcomings. T -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To vie

[google-appengine] Re: The *real* cost of the new billing prices

You are not alone. I suppose EVERY AppEngine guys should be regretting what they have said and done in the past 3 years. -- 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

  1   2   >