I made the changes to be thread safe in all but the configuration utility... That way I can start load and error testing it. I'll let you know the results. (yes it took less than 10 minutes) (but that's because I'm a genius.... or be because Nick Johnson has such a great article on how to do it. http://blog.notdot.net/2011/10/Migrating-to-Python-2-7-part-1-Threadsafe )
-----Original Message----- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Brian Quinlan Sent: Monday, November 21, 2011 12:47 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Want my money back, What should I do? Hi Brandon, On Tue, Nov 22, 2011 at 7:36 AM, Brandon Wirtz <drak...@digerat.com> wrote: > Fine. Post your problems and get them fixed, don’t complain that you > used services you don’t want to pay for. > > > > Yes 2.7 frontends take longer to load. Reduce the number of imports, > and create a warm up script that only does the bare minimum, (doesn’t > handle a request just says “hello I’m up with all the imports”) > > > > Backends don’t support Channels because they aren’t Front ends. > Backends are designed for talking to front ends only, channels are > designed to talk to users. Ergo no channels on the back ends. > > > > BackEnd SDK broken is too nebulous can’t help you. > > > > 2.7 Thread Safe works it is just a PITA to implement, so stick to 2.7 > with thread safe off you get concurrency, and doesn’t require any code changes. I'm not sure what you mean here. If threadsafe is set to "no" or "off" then your instances will not be sent requests concurrently. Cheers, Brian > > > > Without code can’t help you on the 10x as long as usual. Likely based > on the things you have said, those are also user error. > > > > GAE is not like hosting on a physical machine, or like using Amazon. > There are lots of very strict rules for development. If you break > those rules your code won’t scale, you will spend a fortune, and badness will ensue. > > > > You keep saying my cheap food example doesn’t apply, but you keep > making it complicated. You either used the service and owe money. Or > you didn’t and don’t. > > > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Andrius A > Sent: Monday, November 21, 2011 12:11 PM > > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Want my money back, What should I do? > > > > Brandon, your cheap food example here does not make any sense here. > Problems we are having here that we are paying for the services which > do not fully work. I am using GAE since early days and was happy with > the issues before because they didn't cost me a lot. Now GAE came out > of the preview release with drastically increased prices and the > features they advertise do not fully work, for example: backends SDK > broken, backends do not suppor channels API, all my backends stop > working 2-3 times per day, time to time frontends fail to load > throwing deadline exceeded errors, time to time requests to frontends > take 10 times longer even (processing time is as usual), enabling > multi threading with python 2.7 makes things even worse. I am > disappointed because I spent nights trying to adapt changes for new > billing method later to find out that those new features do not actually work! > > > > On 21 November 2011 19:37, Brandon Wirtz <drak...@digerat.com> wrote: > > I run 2.7 Have for weeks. But from where I am sitting you had the > option to eat somewhere else. If you had reached out to Google and > said “Hey, I want to stick with GAE but you have to fix these things > if you want more money”, and they had agreed that would be one thing. > But you instead are in the dine an dash scenario. I at this food, and > now I want a refund because it cost more than I wanted it to. > > > > They gave you a tool to tell you how much the new costs would be long > in advance. They gave you slider nobs so that if you wanted to lower > your performance you could keep the pricing you used to have. > > > > If your cost went up it is because you didn’t gimp your performance. > Is it shitty that things cost more? Yes. Is it Google’s fault you > didn’t turn the sliders, bail, or implement fixes to reduce costs? No. > > > > I on the other hand: > > Saved 20% by implementing 2.7 for concurrency. > > (I do not use thread safe) > > > > Saved 25% by Fixing my cache headers (with minimal documentation on > how to do so) > > > > And as a result the costs are not significantly higher on Release than > they were on pre-release. > > My bill is higher because I merged most of my apps in to one > mult-tenant app so a bunch of 28 hours of instances stopped being free…. > > > > But yeah, you are wining (one N not two). If you get the 90 day > notice that your rent is going to increase, vacate or don’t complain > when your bill is higher. > > > > > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Kaan Soral > Sent: Monday, November 21, 2011 11:21 AM > > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Want my money back, What should I do? > > > > Thanks for your support Andrius, christof > > - And Brandon > > You really make no sense to me, > Let me try to explain you the situation with a similar analogy: > > Burger King decides to roll out a Frequent Eaters Card (will be > referred to as FEC from now on). > I get a FEC to pay at least %50 less when I eat at Burger King But > Burger King's FEC system doesn't function, they tell me that a problem > occurred and they can't issue my FEC, but I am a Burger King addict, > and despite the FEC problem, I still keep on eating at Burger King for days. > > So FEC is Python 2.7 here. I got it, but it doesn't work. > > Should Burger King cover my losses? > ---- > > To give a real life example, above scenario happens a lot on > supermarkets here in Turkey, they keep rolling out promotions, but at > the check out, they almost never get recognized, I am sure this is a > marketing strategy, since a lot of people are careless, they probably > earn a lot malfunctioning so, but they ALWAYS cover your losses when > you ask them > > I am not saying Appengine is malfunctioning on purpose, I know that > there are problems, and they are trying very hard to fix them, but I > am just hoping they would cover our losses > > -- > 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/-/UdWC-vHMDR0J. > 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. > > > > -- > 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. > -- 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.
