[google-appengine] Re: Cloud Storage Or BlobStore
Aswath, I would use Cloud Storage. That is the direction things are heading. Mike On Tuesday, July 3, 2012 10:09:01 PM UTC-5, aswath wrote: Hi, What is the storage recommended to store documents/images while developing applications on appengine. What is better supported in terms of API/backups. Which supports namespaces? Regards, -Aswath -- 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/-/UJylcglnxZ0J. 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: App Engine-related G+ Hangout: WebFilings presentation, Thu 10th May, 6:30pm CDT (4:30pm PDT, 11:30pm UTC)
check here for the hangout when it starts. https://plus.google.com/109136855341297709165/posts On Thursday, May 10, 2012 3:46:32 PM UTC-5, Amy Unruh wrote: Reminder: this hangout is today, starting in a few hours. The broadcast will begin at about 6:30pm CDT Thu 10th May (4:30pm PDT, 11:30pm UTC). On 8 May 2012 17:30, Amy Unruh amyu+gro...@google.com wrote: hi all, This week we will have a fantastic G+ hangout, as we broadcast an App-Engine-related Python User Group presentation by WebFilings, who have lots of experience building large App Engine applications (Robert Kluin and Mike Wesner, whom you may know from this group, will be amongst the presenters). A very special guest, Guido van Rossum (who needs no introduction as the creator of Python and is the author of the App Engine ndb library), may also pop in via the hangout! https://www.webfilings.com/form/python-user-group-may-10th-webfilings The meeting begins at 6pm CDT, but the actual broadcast will begin at about 6:30pm CDT Thu 10th May (4:30pm PDT, 11:30pm UTC). We are starting to announce these hangouts on https://developers.google.com/events/, and you can find this one there: https://developers.google.com/events/ahNzfmdvb2dsZS1kZXZlbG9wZXJzcg4LEgVFdmVudBi04O4BDA/ When the hangout starts, you can find the broadcast here: https://plus.google.com/109136855341297709165/posts . Find when the hangout starts in your time zone: http://goo.gl/KiIjo . View and subscribe to calendar events for these hangouts here: http://goo.gl/GGkgx , http://goo.gl/PILq0 . -Amy -- 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/-/R45E8MBnyQcJ. 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: Indexing a monotonically increasing value: How much does it limit write throughput?
I'd also like to know if this is any different on high replication than it was on master slave. (I know its a lower level bigtable side effect, but does hrd/paxos deal with it differently?) Are you planning on writing these entities at hundreds of qps? Most of the conversations I have had about this revolve around the entity key rather than the indexes, but I suppose you could create a similar problem there. Have you done any tests? This might be one thing that is better to actually test even if you get a solid answer here. Mike On Monday, May 7, 2012 8:01:14 AM UTC-5, Michael Hermus wrote: All, I have read in several places that using a monotonically increasing value for a key or in an index is a bad thing, primarily because of the way Big Table manages the process of splitting overloaded tablets. In a few comments, I have read that it really isn't an issue unless you hit around 300 QPS. There are many cases where I would like to use timestamp in an index (to order or limit query results based on creation time, for example). So, my questions are: 1) Is there a definitive issue with throughput when using a timestamp in an index? 2) If yes, what is the approximate QPS threshold where it becomes an problem? 3) What can we expect after exceeding this threshold? 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/-/FHUqvBlr6gQJ. 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: $500 support - your experiences
Well, coming from people running a business on app engine I can say that it has been valuable to us. We run into situations where something strange occurs and we are able to create a ticket and get a very fast response from the support team. They have a direct line of communication with the SRE team and all the engineers for the various features of app engine. We have some the best app engine talent working with us and write great stuff, but it is still important to have operational support to ensure our customers have no interruption in service and at the best possible quality. Unless you want to depend on this list and stack overflow and the random yahoos that are happy to offer various opinions to you. I suggest you work with Google directly. Mike On Saturday, April 14, 2012 4:42:56 AM UTC-5, Richard Watson wrote: Just wondering: what are the experience of App Engine customers that pay for $500/month support? For a significant app I would think it's a no-brainer if it has enough benefit. -- 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/-/86f7LaVXA5AJ. 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: High latency in HRD app. HELP!
Hopefully someone on the Google team can take a look for you. I have a few questions and things for you to try. 1. How young are your instances? are you seeing instance churn? 2. Can you post your app settings, max idle, how is your traffic? spikey? 3. Do you see the same issues on other appids? (do you have a test instance setup somewhere for QA or staging?) You might just be in a bad spot somewhere or it could be a legitimate issue based on your settings and some part of your application causing churn or other issues. We have seen some of the best performance on HRD in a long time over the last 2 weeks or so. Mike On Wednesday, April 11, 2012 8:15:10 AM UTC-5, Nicanor Babula wrote: appid: domodentweb2 datastore: High Replication normal latencies: 50-200ms today's latencies: 1000-6ms Dear Appengine Team, Google appengine is a wonderful product and gives us satisfaction seeing our app solving our customers problems every day. Thanks to appengine, we provide to our customers a web-based solution as fast as a desktop. Our customers are our fans. They were complimenting us for the app. Unfortunately, the dream seems to be over, as our app started encountering high latencies out of nothing. The first time we thought it was an isolated case (bad things happen to anybody, don't they?). As of today, we are encountering AGAIN high latencies. I think is the third or fourth time in less than 40 days. At a closer look, instances seem to either get restarted or disappear from the instances page for a few minutes. The same code version that worked fine yesterday, today is slow. Customers are upset and are calling us, saying that the app is so slow, it cannot be used. In fact the user experience is poor right now. The app is very slow. We don't know what to tell them anymore, since this happened again recently. Soon we'll start losing customers. What can we do in this situation? Do we have to migrate to Premier account in order to have low latencies? Or the resources are the same for everybody? If so, what do we have to do in order to migrate? Please, Google Appengine Team, let us know something. Thanks and keep up the good work, Cristian Nicanor Babula and the Domodent team -- 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/-/gmA-FdnzqQcJ. 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: High latency in HRD app. HELP!
Your app will run well if you use auto for max idle instances, but you should not have to do that and it is expensive. When things are running like they should you can tune it based on your traffic. Ours is very smooth so we can safely set it to a fairly low setting and it runs well. We leave some room for an odd process to spike our average latency (and thus spin up instances). That could be your issue though. Depending on how much traffic and how much it varies, 6 idle instances might not be enough to handle the ramp up and it's choking out your users. (not enough instances for the traffic spikes) What I meant by churn is lots of instances dying (from memory limits, errors or unknown infrastructure issues) or shutting down due to your max idle instances being too low for your ramp up/down rates and then getting started again. On Wednesday, April 11, 2012 11:07:55 AM UTC-5, Jeff Schnitzer wrote: On Wed, Apr 11, 2012 at 11:30 AM, Nicanor Babula nicanor.bab...@gmail.com wrote: Hi Mike, Thanks for your answer. 1) The ages of the instances span from 8 minutes to 30 minutes. What do you mean by instance churn? 2) Idle instances: 1 - 6 Pending latency: Automatic - Automatic I presume you mean you have Min Idle Instances set to 1 and Max Idle Instances set to 6. Set these to Auto-Auto. It's been a couple months since I last touched these settings, but every time I did I got a crappy UX with lots of user-facing loading requests. Since going to Auto-Auto our app has been consistently snappy. Jeff -- 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/-/p3BNM_Fs4bUJ. 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: How can i increase indexes of my application
The 200 limit made sense before the new billing scheme, but now it doesn't as much. We pay (a lot!) for storage and the additional datastore operations that result from having more composite indexes. This limit should probably be removed entirely. Mike On Wednesday, March 21, 2012 2:47:06 AM UTC-5, prakhil samar wrote: Hi I have a application and my datastore indexes are full i have created 200 indexes. is there any way that indexes can be increased ? Can i increase indexes by enabling billing on my application ? -- 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/-/RSyf_nV1G4MJ. 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: Which CapabilitySet checks go with HRD?
Wow, I haven't even thought about capability api since we moved to HRD way
back when. HRD FTW!
Mike
On Friday, March 2, 2012 8:37:34 PM UTC-6, Philip wrote:
I used to use...
from google.appengine.api.capabilities import CapabilitySet
if (settings.MAINTENANCE_MODE or
not CapabilitySet('datastore_v3',
capabilities=['write']).is_enabled() or
not CapabilitySet('memcache',
methods=['set']).is_enabled()):
...to determine if app engine was in maintenance mode.
Now that I have migrated apps to use HRD, instead of the old Master/
Slave datastore, what capability set checks should I use to determine
if the app should be set automatically in maintenance mode?
--
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/-/pL96vDr1QPQJ.
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: Python 2.7: Instance memory limitations with concurrent requests
I know that, but I thought it might still be relavant. On Feb 21, 3:13 pm, alex a...@cloudware.it wrote: The whole point of this topic was python27 runtime, multithreading and concurrent requests. Your specific case, plus python 2.5, doesn't necessarily means memory leaks in the runtime itself. I'd profile my code that handles most frequently accessed URLs to start off. -- 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: 2012 US PyCon -- GAE Related Sprints
What Robert meant by several colleagues is some guys from WebFilings. Shameless plug, we are also looking for talented developers to join our team, so look us up if you are interested. -Mike On Feb 21, 12:46 am, Robert Kluin robert.kl...@gmail.com wrote: Hey Everyone, Myself and several colleagues are going to be at pycon, and sticking around for a few days of sprints after the main conference is over. We're planning to discuss and work on several App Engine related projects during that time. Some of the projects are pretty neat, and should benefit the larger App Engine Python community. We'd also love to have some help or more ideas for cool things to work on! If you're going to be at PyCon and sticking around, feel free to sign up or just catch one of us at the conference. Feel free to stop by even if you'd just like to nerd-out about App Engine / Python! Some current items on the project list: - An ext.db mock for unit tests that offers basic functionality (including querying!) without the poor performance of the SDK stub. - Work on PyAMF and RTMPy. - Since we'll soon have pull-queue tagging, I want to get out the updates I've been holding back for slagg. - I'd like to put together a Cassandra stub for the SDK. I made good progress on this last year, but it has fallen behind. I've added our spint to the pycon sprints page, see APP ENGINE RELATED PROJECTS (COMMUNITY RUN) https://us.pycon.org/2012/community/sprints/projects/ Robert -- 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: Task Queue Quota Errors, but I have enough quota
The bucket and rates are for controlling execution. They don't limit adding tasks to a queue. -mike On Feb 10, 12:47 am, Brandon Wirtz drak...@digerat.com wrote: Did you tweak your buck and token rate? I have never tried to see how far I could take it. -- 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: Task Queue Quota Errors, but I have enough quota
They payloads of the tasks count towards the store bytes quota. So that does limit how many you can add to the queue, but that is not the issue here. The bucket/token stuff doesnt impact adding to the queue. from the docs... The task queue uses token buckets to control the rate of task execution. Each named queue has a token bucket that holds a certain number of tokens, defined by the bucket_size directive. Each time your application executes a task, it uses a token. Your app continues processing tasks in the queue until the queue's bucket runs out of tokens. App Engine refills the bucket with new tokens continuously based on the rate that you specified for the queue. On Feb 10, 2:52 pm, Brandon Wirtz drak...@digerat.com wrote: The bucket and rates are for controlling execution. They don't limit adding tasks to a queue. Doesn't the Token bucket? Also there is a max QueSize in MB you can specify in the YAML. I don't know what the limit is. My rough understanding was that Token Rate was how many task/s you could add. Process rate was how fast tasks would be processed. Queue Size was number of tasks that could be pending. Time Out was the time to expire If your token rate is 5 per S And your process is 2 per And your Queue size is 5000 And your time out is 75 minutes If 18 people wanted to make 10 new tasks in 3 seconds. The Token bucket would empty and only 15 tasks would be created. If 500 people an hour wanted to create 20 tasks each (1 tasks, 3600 seconds) yields 2.78 Tasks/s the Token bucket would not go dry. The Process bucket would spin up instances enough to process the tasks, and it would try to space them out such that it would take 5000 seconds But you would lose some of those task because the Task Queue would not have only processed all of the tasks before it hit the 5000 task limit (7200-ish would complete) And because you are limiting tasks to 75 minutes, but it would take 1 hour 23 minutes to process the task a portion would get dropped. -- 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: Indexes
Would be great to hear from the App Engine Team about this. It seems like one area that has never had any attention. Work could be done to: 1. Speed this process up or at least inform the user of the ETA 2. Explain why an index goes into error, or better yet just never let them be in error 3. Allow the user to fix the index by clicking on something if its in error (remove and re-index button?) -mike On Feb 10, 4:25 pm, Barry Hunter barrybhun...@gmail.com wrote: If you mean a custom composit index (ie via index.yaml) - then I believe there is a sequential processing queue. The delay is as much about how many tasks (and their size!) are in the queue, rather than the size of your new index. Unless its stuck in some sort of error state - check your logs. In which case might need to do some vacuuming On Fri, Feb 10, 2012 at 6:30 PM, Christian Goudreau queen...@arcbees.com wrote: Hi Everyone, Why my indexes takes forever to build while there's only two object? And two field? -- 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/-/uQ7fzt6wy6IJ. 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.
[google-appengine] Re: SLOW
Robert's tuning has done very well for us in various situations. Running a large diverse app takes a balance of these settings. When you factor in task queue performance and such, it can be a little weird. The rules are going to be different for every app, so I don't think you can have a magic formula. It really comes down to a balance of what you want to pay vs the risk you want to take of a spike causing issues for customers. -Mike On Feb 7, 12:55 am, Brandon Wirtz drak...@digerat.com wrote: Did you factor into account app startup times? Some apps can easily take several seconds to get fired up, so they do better with a larger buffer. For light apps I agree, I've found 1 or 2 is sufficient. Yeah, I said warm-up not startup, but same thing. I like lower numbers too, but if your max latency is at 1/3 your average you will pretty much be guaranteed to have an instance per simultaneous request. My average request is 300ish MS so I can pull off 500-600ms, but someone with 2.5s average would spin up a lot of extra instances everytime a user hit a page making 8 requests. And you'd eat the start up time on all those instances, so too low of a Max can make things worse. Again check the archive I talked about this too. -- 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: Funny spikes in graphs
Have you looked at the logs to see what/who is making the requests? It could be some type of polling or service that is making requests at those intervals. -Mike On Jan 31, 8:40 am, Andrin von Rechenberg and...@miumeet.com wrote: Hey there My dashboard shows funny spikes in all graphs (qps, bandwidth, ram). It's been doing this for a couple of days now. ProdEagle shows everything is fine, so I guess something must be messed up on Google's side... Anyone else seeing this? Cheers, -Andrin Screen shot 2012-01-31 at 3.38.39 PM.png 56KViewDownload -- 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: Trusted Advisors
Robert and I and others were working on the Google Certified Developer program for App Engine but that got put on hold. I would love to see that picked back up at some point. We put a lot of time into that. It would need updated since so much has changed, but I do think it would boost the community. It wasn't just the exam, it also required contributing to the App Engine community. -Mike On Jan 31, 8:30 am, Barry Hunter barrybhun...@gmail.com wrote: Isnt that 'service' jsut a bunch of automated tests run against your stack? You seem to be suggesting, some sort of 'qualification' or 'accreditation' for others. Pretty much ashttp://code.google.com/qualify/ used to do? On Tue, Jan 31, 2012 at 10:29 AM, Brandon Wirtz drak...@digerat.com wrote: I got this email from AWS, and thought, GAE Should have those… ** ** *AWS Trusted Advisor: *Building on our aggregated history of serving hundreds of thousands of customers, the AWS Trusted Advisor program is a best practices auditing service that monitors a customer’s use of AWS services and automatically recommends configuration changes or new services that may save money, improve system performance, or close security gaps. AWS has built systems to regularly run best practice feature checks against a customer’s AWS environment to flag potential opportunities for improvement. AWS Trusted Advisor launches with 8 checks and additional ones will be continuously deployed throughout the year. A more detailed description of AWS Trusted Advisor can be found in Jeff Barr’s Blog.http://www.amazon.com/gp/r.html?R=Y3D28NHF8W0RC=2FN2VE46VDVGFH=6HAX... ** ** I was a Microsoft MVP, and MCSE, and “Gold Certified Partner” so I get the whole dub people community leaders so all the kiddies will rush off to pad their CV as a great way to build an expert base. It works well. ** ** ** ** *Brandon Wirtz *BlackWaterOps: President / Lead Mercenary [image: Description: http://www.linkedin.com/img/signature/bg_slate_385x42.jpg] *Work:* 510-992-6548 *Toll Free:* 866-400-4536 *IM:* drak...@gmail.com (Google Talk) *Skype:* drakegreene *YouTube:* BlackWaterOpsDotComhttp://www.youtube.com/blackwateropsdotcom ** ** BlackWater Ops http://www.blackwaterops.com/ Cloud On A String Mastermind Group http://www.cloudonastring.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. image001.jpg 1KViewDownload -- 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: Considering a Cloud MasterMind Group
I really don't think you need to fill the silence with posts when this list has a slow day. Generally people who work with different cloud platforms are ok with visiting a couple of different discussion sites to talk about each platform. I see no reason to combine them, but you feel free to do so. -Mike On Jan 25, 10:09 am, Brandon Wirtz drak...@digerat.com wrote: Yeah but those are all Goog specific. They aren't General Cloud. Most groups don't have a strong moderator to keep the discussion flowing. You may or may not notice, on days when there are no posts to this list I make sure to post something to discuss, that isn't necessarily a problem. I do this to keep the smart people engaged, because if all the people smarter than me leave, I'm just talking to a room full of people who can't answer hard questions for me. :-) But I'd like to get all those smart people engaged on a regular basis, and help make them smarter. Does that make sense? I think I have talked myself in to it. I'll post details later, but I have been up since I don't know when but more than 24 hours and I need to crash. -Original Message- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Robert Kluin Sent: Wednesday, January 25, 2012 7:23 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: Considering a Cloud MasterMind Group Hi Brandon, So there are already several venues where some pretty talented users hangout. There are also office hours held twice per month, these sometimes attract decent groups and sometimes don't. There are also a couple groups of skilled developers (sometimes including core app engine team members!) who occasionally have informal hangouts (in the Google+ sense) to discuss things. I know some video logs from these have been posted to youtube so that others can reference them as well. There have been several efforts in the past to do things like this; I've not seen any that really consistently attract a group for discussions. Robert On Wed, Jan 25, 2012 at 08:00, Rohan Chandiramani masterxr...@gmail.com wrote: I see where you are going now, and i think it's a legitimate and realistic goal. Still i'm pretty sure there is a big demand for a best-practice wiki, but that's a different project then. That leaves all the nasty issues to this board. Do you have an implementation in mind, another groups or a reddit-like approach? -- 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/-/MLyi7hr7gy8J. 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 athttp://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.
[google-appengine] Re: 1.6.2 Pre-Release SDKs Out
Thanks to the task queue team for the help recently, and for adding TaskETA header for debugging some things. -Mike On Jan 24, 1:09 pm, Robert Kluin robert.kl...@gmail.com wrote: Look like some good changes / improvements are coming. Robert On Tue, Jan 24, 2012 at 10:58, Marzia Niccolai marce+appeng...@google.com wrote: Hi, The 1.6.2 were uploaded yesterday. Release notes are below. - Marzia Java Version 1.6.2 ===- The Admin Console Datastore Admin has added experimental backup and restore functionality. The job occurs within your application and counts against your application quota, including Instance Hours, Datastore Ops and Datastore Storage. - Channel API quota is now automatically measured in terms of minutes a channel has been open, instead of channels created. Additionally, developers can now specify how long a channel can be open, with the default remaining two hours. - Task Queue API requests now include a X-Appengine-TaskETA header, that can be used to measure task delivery latency. - We have removed the deprecated labs version of the TaskQueue API. - The default API deadlines for Blobstore API calls have been raised to 15s for online and 30s for offline requests, up from 5s. - The Images API now allows you to stretch an image without maintaining the aspect ratio. http://code.google.com/p/googleappengine/issues/detail?id=2220 - Fixed an issue where the SDK did not resize images down to 512 pixels by default, as it does in production. - Fixed an issue with the Images API where valid images were returning a NotImageError. http://code.google.com/p/googleappengine/issues/detail?id=5545 Python Version 1.6.2 - The Admin Console Datastore Admin has added experimental backup and restore functionality. The job occurs within your application and counts against your application quota, including Instance Hours, Datastore Ops and Datastore Storage. - Channel API quota is now automatically measured in terms of minutes a channel has been open, instead of channels created. Additionally, developers can now specify how long a channel can be open, with the default remaining two hours. - Task Queue API requests now include a X-Appengine-TaskETA header, that can be used to measure task delivery latency. - The default API deadlines for Blobstore API calls have been raised to 15s for online and 30s for offline requests, up from 5s. - The Images API now allows you to stretch an image without maintaining the aspect ratio. http://code.google.com/p/googleappengine/issues/detail?id=2220 - The Blobstore API now includes the asynchronous function calls create_upload_url_async, delete_async, and fetch_data_async. - Django version 1.3 is now available in the Python 2.5 runtime. - We've added a django_wsgi builtin to allow easier bootstrapping of Django applications. - Fixed an issue with remote_api where calling fetch_page() with a page size of 301 and chaining the calls through the returned cursor was skipping half of the results. - Fixed an issue where the PIL _imagingmath module was not available in Python 2.7. - Fixed an issue where the SDK did not resize images down to 512 pixels by default, as it does in production. - Fixed an issue with the Images API where valid images were returning a NotImageError. http://code.google.com/p/googleappengine/issues/detail?id=5545 - Fixed an issue where the SDK didn't start when using Python 2.7 and the --backends flag. http://code.google.com/p/googleappengine/issues/detail?id=6187 - Fixed an issue where Jinja2 was not included in the SDK for use with Python 2.7. http://code.google.com/p/googleappengine/issues/detail?id=6265 - Fixed an issue with the sql datastore stub in Python 2.7 where the sqlite module no longer accepted strings with non-ASCII characters. http://code.google.com/p/googleappengine/issues/detail?id=6290 - Fixed an issue where gzip did not work with Python 2.7 in the dev_appserver. http://code.google.com/p/googleappengine/issues/detail?id=6324 - Fixed an issue where urllib2 did not work with Python 2.7. http://code.google.com/p/googleappengine/issues/detail?id=6567 - Fixed an error in the Datastore Viewer where an error was thrown when viewing an Entity which defines an index with no properties. http://code.google.com/p/googleappengine/issues/detail?id=6600 - Fixed an issue where transactional tasks were not enqueued in the SDK when running in high_replication mode. http://code.google.com/p/googleappengine/issues/detail?id=6669 -- 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,
[google-appengine] Re: Request count?
Quota Details page, first item listed. On Jan 6, 6:13 pm, Brandon Wirtz drak...@digerat.com wrote: When there was a quota limit for it, there was a number of requests counter. Is there some way to get that number still? I was interested in calculating the cost per request and couldn't really find it. Analytics doesn't work because bots don't count in them, and a single page might be 100 requests. -- 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: Worst-case scenario for eventual consistency in the HRD?
I don't think Ikai read your post... Robert and I wanted to write a little HRD status site to track this and get real data, but we haven't done so yet. I have never seen the replication take more than about 1s. I think 1s will cover about four 9's, but that is just an educated guess. Until we (the users) actually measure this over time I don't think we can know for sure. -Mike On Sep 19, 7:16 pm, Jeff Schnitzer j...@infohazard.org wrote: I know that an index update in the HRD will typically be visible within a couple seconds. That's the average case. What is the worst-case? Assuming something in the datacenter goes wacky, how long might it take for an index to update? Tens of seconds, minutes, hours, days? Thanks, Jeff -- 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: Worst-case scenario for eventual consistency in the HRD?
And then I went and used the word replication... i meant index lag. On Sep 20, 9:40 am, Mike Wesner mbwes...@gmail.com wrote: I don't think Ikai read your post... Robert and I wanted to write a little HRD status site to track this and get real data, but we haven't done so yet. I have never seen the replication take more than about 1s. I think 1s will cover about four 9's, but that is just an educated guess. Until we (the users) actually measure this over time I don't think we can know for sure. -Mike On Sep 19, 7:16 pm, Jeff Schnitzer j...@infohazard.org wrote: I know that an index update in the HRD will typically be visible within a couple seconds. That's the average case. What is the worst-case? Assuming something in the datacenter goes wacky, how long might it take for an index to update? Tens of seconds, minutes, hours, days? Thanks, Jeff -- 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: Unexpected Entity Group transaction contention
Any time you write/update an entity in a group (share a common ancestor) you lock the entire entity group all the way to the top most parent. All branches under that parent... the entire tree. Multi eg transactions will allow you to write to multiple groups but it will not reduce contention in this scenario at all. Mike On Sep 13, 2:23 pm, Brian Olson br...@cloudlock.com wrote: Re-reading the documentation, this kinda makes sense, but it bit me recently so I want to tell the story and see what others think. I make an entity Parent(). Some time later I make an entity Child(parent=some_parent) and I do this in a transaction. I do this a bunch, concurrently from task-queue entries. I was surprised to learn that simply creating a Child in a transaction, without otherwise doing anything to the parent, neither .get() nor .put(), locks the parent and all its children. def txn_make_child(some_parent): foo = Child(parent=some_parent) foo.put() # also transactionally enqueue a task to operate on the Child instance foo Code very much like that was failing out due to too many transaction retries. I didn't expect *any* transaction contention, because I thought I was just creating an object and enqueueing a task, and those were the only two things in the transaction in my head. But it turns out the above code locks some_parent and all its children. Boo. I think I was expecting things like this to lock parent and all its children: def txn_p_c_example(parent_key, child_key): parent = db.get(parent_key) child = db.get(child_key) # now they're clearly both involved, and involving the parent winds up locking all the children. I can accept that. parent.put() child.put() I was able to re-code it to make Child have no ancestor, but there are still times when I would much rather still commit parent and child at exactly the same time. -- 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: Outrageous Gae New Pricing Increase
Please stop telling people to use these settings. Nobody will use the damn service if they have to wait for seconds for a request to load. Please either setup an app to run well and pay for it or use something else. I am a bit surprised that 15s is even an option for min-pending latency... that is just crazy. On Sep 7, 1:40 am, renderpaz kev...@gmail.com wrote: But maybe there is a solution... I'm going to take a guess and say that most of your cost is instance hours - make sure you change your min-pending latency to 15s and your max idle instances to 1 -- 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: Even the HR Datastore is (slightly) having performance issue now.
Thanks for putting those together. It very clearly shows that recently things have changed. It would be nice to hear from Greg or someone about this. -Mike On Sep 6, 7:11 am, Simon Knott knott.si...@gmail.com wrote: I've attached graphs showing the daily stats for each of the HR operations for the last year, driven from the GAE Status stats. I'll grab the M/S datastore statistics, when I get the time, to give a comparison. https://lh4.googleusercontent.com/-MV_ixL3Jz0Y/TmYNsX9QEGI/AF... https://lh4.googleusercontent.com/-6yrWNd7wfxU/TmYNoldrFWI/AF... https://lh6.googleusercontent.com/-NiRHqyRtbro/TmYNgZLeRXI/AF... https://lh3.googleusercontent.com/-WGYYZUzXiAg/TmYNk35ZztI/AF... https://lh5.googleusercontent.com/-5GRqG-Sy17A/TmYN7E7C60I/AF... -- 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: calling /_ah/warmup is bad under new price model?
It is not useless. It does the exact same thing it did before, gets your instances hot so that they can serve user facing traffic as quickly as possible (without the startup overhead). Making your code perform well and it's cost are no longer aligned under the new pricing. On Sep 5, 3:04 am, Tapir tapir@gmail.com wrote: I think it is totally useless now. It conflicts with number s of idles instances setting. Tim Hoffman wrote: I would think your mad to use a framework with a typical startup time for an app instance of 10 secs if your only going to serve 100 requests a day. As I said the value of /_ah/warmup depends on the situation. Tim -- 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: calling /_ah/warmup is bad under new price model?
In order for them to be idle, they must start. They can either start as a result of a user facing request or a warmup request. If you don't want your users to suffer the latency or your instance startups, then warmup requests are still relavant. I do understand the new scheduler settings. Let me know if I can answer any of your questions. ;) -Mike On Sep 5, 8:29 pm, Tapir tapir@gmail.com wrote: Do you understand the new app settings?! If you have 3 idle instances, warmup is just waste your money. On Sep 5, 11:04 pm, Mike Wesner mike.wes...@webfilings.com wrote: It is not useless. It does the exact same thing it did before, gets your instances hot so that they can serve user facing traffic as quickly as possible (without the startup overhead). Making your code perform well and it's cost are no longer aligned under the new pricing. On Sep 5, 3:04 am, Tapir tapir@gmail.com wrote: I think it is totally useless now. It conflicts with number s of idles instances setting. Tim Hoffman wrote: I would think your mad to use a framework with a typical startup time for an app instance of 10 secs if your only going to serve 100 requests a day. As I said the value of /_ah/warmup depends on the situation. Tim -- 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: Latency values on dashboard
I'll take a shot at this... The latency graph (milliseconds/request) shows you the average of the 'ms' field from the logs. The wall clock time of the request including the startup time for the instance. The logs also indicate if the request was a new/loading request. If I understand your question correctly... There isn't really any time waiting for a request. No matter what the scheduler decides it's going to make a request, new or existing it's your code that is using the time to 'startup'... python imports, framework, loading that stuff from disk... that is what takes the startup time. Is that what you mean or are talking about pending_ms/throttle_code? -mike On Sep 5, 8:42 pm, GAEfan ken...@gmail.com wrote: Do those request latency values include the time waiting for a new instance, or does the clock start after loading into and running in the instance? If the former, where it represents the total latency of every request, then we can properly measure the effect of changing the instance sliders. Please clarify. -- 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: Even the HR Datastore is (slightly) having performance issue now.
I would be interested in what the gae team has to say about this. It seems exactly the same as the evolution of the master slave data store. Its latency creeped up over the first few years and became pretty unstable. Definitely concerning. Mike On Sep 1, 9:30 pm, Raymond C. windz...@gmail.com wrote: http://code.google.com/status/appengine/detail/hr-datastore/2011/09/0... Compare it to half a year before:http://code.google.com/status/appengine/detail/hr-datastore/2011/03/0... It seems to me that HRD was so stable because there was not much applications on it (just like back in the day M/S was not having so many downtime and performance issues) -- 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: Even the HR Datastore is (slightly) having performance issue now.
Yes, I agree that it won't (can't) get as bad as m/s did get because HRD is awesome. My concern is mostly over how they provision and that the latency is that much higher than it was. Why does the load have such a big impact on latency of datastore query? We keep very detailed statistics about the latency of our services and its clear by our average latencies that it has creeped up over time. It is roughly 200ms higher than it was when we first moved over to HRD. Mike On Sep 2, 8:16 am, Tim Hoffman zutes...@gmail.com wrote: Hi Actually I would disagree on the M/S front, all of my apps are on M/S and even despite the recent issues M/S is way more stable than it was in 2008 and 2009, I mean WAY MORE STABLE ;-) Thats not to say more growing pains won't be felt. My guess is with a supposed imminent exodus of apps, we may say some performance improvements across the board ;-) Rgds Tim -- 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: Does datastore pricing prevent pubsub?
I am guessing Brett doesn't have to foot the bill for this. Uncle Google picks up the tab since he works for them. On Sep 2, 8:31 am, Dennis Peterson dennisbpeter...@gmail.com wrote: Maybe I should explain...the details don't matter, the key point here is that the design in the GoogleIO talk involves a separate entity for each post. Google charges a buck per 10K ops, so if each post returned is an op, then a hundred pageviews showing a hundred posts each is a buck. That seems pretty outlandish. Is it really correct or am I missing something? On Thu, Sep 1, 2011 at 1:03 PM, DennisP dennisbpeter...@gmail.com wrote: Last I saw Google was defining each entity returned as an operation.. If you were building a social network or twitter clone using the techniques Google recommends in this talk: http://www.google.com/events/io/2009/sessions/BuildingScalableComplex... ...you could easily pull back a hundred entities each time you pull someone's feed. It'd cost you a buck for every hundred pageviews or so. Do I have that right? -- 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.
[google-appengine] Re: UNBELIEVABLE NEW BILLING!! Google Please respond...
and just so everyone knows, you can change this field after existing data is there and next time you put/write the entity the impact will be reduced. It is a good practice to always set indexed=False unless you know you need the single property index or if you want to use it in a composite index (index.yaml). On Sep 1, 5:33 pm, Kaan Soral kaanso...@gmail.com wrote: WOW, Im glad I took the time and added indexed=False to wherever possible On Sep 1, 8:20 am, Robert Kluin robert.kl...@gmail.com wrote: Hey Mike, The difference is due to indexes. Every index write is a datastore operation too. So if your entity has five indexed properties, you've got another 10 datastore operations per entity written. Robert On Wednesday, August 31, 2011, Michael Robellard m...@robellard.com wrote: Dear Google, I love Google App Engine, but right now I am at a loss for what to do. My current billing is $4.98/day. Under the new system it is $34.41/ day, and that is with the 50% frontend discount. The effort that would be involved in porting my app to a different architecture is far beyond what I could accomplish in the next few weeks, and to be honest I don't want to move off of App Engine. I like not having to deal with Sys Admin stuff. I have to imagine that Google did not intentionally raise my serving rates by 700%, so that must mean I am doing something wrong in my code/ design, however I don't know how to fix these problems currently. I have already done a lot of work in the past to memcache things and do multiple gets and puts in a single call, and most of my apps time is spent handling tasks. So I have already done a lot of what is recommended in the managing resources guide. In addition I don't understand how my app says it has 1.05 million reads and 12.3 million writes per day when I look at Appstats and see that I have at least 3 datastore gets for every one datastore put and that's not count next and runquery. Thanks, Mike Railroad Empire appid: railroadempire On Aug 31, 6:51 pm, smwatch showm...@gmail.com wrote: Is it really 10 times the original cost.!! Now we will be paying from $200/month to $2000/month under new billing. Just out of our reach, does not make any business sense to stay with GAE. We spent huge amount of time and effort to learn and develop in Python, and now we are being forced to move out of Google Engine. This completely does not make any sense. Google please respond, you are reading please give us more time to either move off your systems, or compensate for existing users. Giving a email notice of such a short duration and showing Preview of billing so late in the game is just not right. Google please do the right thing to make this billing more gradual. Developers all over, please help show your sentiment. -- 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. -- -- Robert Kluin Ezox Systems, LLC -- 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: Firewall blocks new goog.appengine.Channel(token);
Our customers also generally block talkgadget . It would be best if a channel API endpoint existed on appspot.com, or better yet through our actual appids so that we can give the customer a single domain for which they can allow. They would be able to block everyone else's channel endpoints but allow yours. I starred the issue and added my comment above. Mike On Aug 19, 6:36 pm, steve bonham.st...@gmail.com wrote: Aha! I starred the issue (see link below). The first law of posts, you figure it out immediately following your post. http://code.google.com/p/googleappengine/issues/detail?id=4764 On Aug 18, 2:47 pm, steve bonham.st...@gmail.com wrote: After a day of combing the web, I couldn't figure out why goog was undefined in my javascript on a particular client. Turns out my customer's firewall blocks Google's talkgadget.google.com which is where /_ah/channel/jsapi goes to. I use just about every other component of appengine and haven't found any other problems through this firewall. To solve the problem, I have to check if(goog == undefined) then use an alternative to Channel. If anyone else has a better solution, I'm all ears. Otherwise, sounds like a production ready app will need to be prepared for firewall gotcha's when using Channel. -- 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: Firewall blocks new goog.appengine.Channel(token);
Our customers also generally block talkgadget . It would be best if a channel API endpoint existed on appspot.com, or better yet through our actual appids so that we can give the customer a single domain for which they can allow. They would be able to block everyone else's channel endpoints but allow yours. I starred the issue and added my comment above. -Mike On Aug 19, 6:36 pm, steve bonham.st...@gmail.com wrote: Aha! I starred the issue (see link below). The first law of posts, you figure it out immediately following your post. http://code.google.com/p/googleappengine/issues/detail?id=4764 On Aug 18, 2:47 pm, steve bonham.st...@gmail.com wrote: After a day of combing the web, I couldn't figure out why goog was undefined in my javascript on a particular client. Turns out my customer's firewall blocks Google's talkgadget.google.com which is where /_ah/channel/jsapi goes to. I use just about every other component of appengine and haven't found any other problems through this firewall. To solve the problem, I have to check if(goog == undefined) then use an alternative to Channel. If anyone else has a better solution, I'm all ears. Otherwise, sounds like a production ready app will need to be prepared for firewall gotcha's when using Channel. -- 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: How to force update of all files?
Deploy to a new version. On Jul 8, 1:47 pm, Ikai Lan (Google) ika...@google.com wrote: Do you have additional details? Another way could be to run the command line script: appcfg.sh. It's not the plugin that detects whether files have changed, however. When we upload your application, we compare hashes against files already stored on App Engine and choose not to upload those. Could it be possible you are uploading old files somewhere? Or could it be possible when you test for changed files, that your browser is caching the old ones? Ikai Lan Developer Programs Engineer, Google App Engine Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine On Fri, Jul 8, 2011 at 12:43 AM, inf hooversha...@gmail.com wrote: My Google Plugin for Eclipse 3.7 does not correctly identify all of the files that I have changed in my application. Is there a way to force all files to be updated? -- 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/-/vFplL2dnsawJ. 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.
[google-appengine] Re: FAQ for out of preview pricing changes
Greg, I am concerned about the potential changes to the python front end instances. Currently an instance could use at least 200mb. Soft memory limit errors aside you could bump into the hard limit (MemoryError) at 300mb. I don't think it is wise to change that limit down to 128mb. It really guts the capability of task queues if you reduce the memory further. 10 minutes of processing time doesn't mean much if you are that restricted by ram. Reducing memory on front end instances will break some of our heavy weight features. -Mike Wesner On May 18, 1:33 pm, pdknsk pdk...@googlemail.com wrote: Q: You seem to be trying to account for RAM in the new model. Will I be able to purchase Frontend Instances that use different amounts of memory? A: We are only planning on having one size of Frontend Instance. What's the reason for this? It's completely understandable if Google wants to make (more) money. I'm just curious. -- 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: Do HR-enabled apps get more than one memcached instance?
Your app actually only runs out of one data center at once. The diagram was a little misleading. If a data center goes down then your app is served out of the other with a different memcache (empty) On May 14, 3:26 pm, Sergey Schetinin ser...@maluke.com wrote: I'm pretty sure the memcached clusters (if there are more than one) are not synchronized. First of all, that would be way too slow. Second, the talk I referenced specifically mentions that when the apps are being migrated from a DC, the memcache writes return success but are in fact noop, because synchronizing memcache data does not make sense. So I would expect that there's no synchronization going on during regular operation as well. Anyway, I really hope that there's only one memcached cluster active at a time. On 14 May 2011 22:05, rekby timofey.koo...@gmail.com wrote: I thing HR-applications have more than one syncronised memcache - by me test save in HR-memcache in 3 times slower, than Master/Slave application. On May 14, 6:56 pm, Sergey Schetinin ser...@maluke.com wrote: So, I was watching the presentation on the HR datastore from the IO 2011 (http://www.google.com/events/io/2011/sessions/more-9s-please-under-th... ) and one thing caught my attention: the slides were showing the frontend instances running in more than one datacenter at the same time. So I understand that the memcached can lose data at any time and if the app is migrated between the datacenters all of the data in the cache are lost, however, running the app in two or more datacenters at a time each DC having a separate memcached cluster, that changes the properties quite significantly. For example let's consider an app that uses some memcached key to keep a cursor where to write to the datastore, atomically incrementing it after each write. Such an app can detect if such a key is not present in the cache and determine what the cursor is by doing a query on the database and then add it to the cache atomically. If we add the possibility that there's another DC running the app w/ an independent memcached instance, such an app would just corrupt its own data. I hope I explained my concern well enough, and I would love to hear an answer from someone on the App Engine team. Thank you. -Sergey --http://self.maluke.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 athttp://groups.google.com/group/google-appengine?hl=en. --http://self.maluke.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.
[google-appengine] Re: ApplicationError: 1 Too many indexed properties for entity
5000 On Apr 25, 3:40 am, ZS zimon.spa...@gmail.com wrote: Anyone knows the App Engine limit? (How many indexes can I use on a single property?) -- 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: ApplicationError: 1 Too many indexed properties for entity
I guess I should be more specific. You can have 5000 indexed items per entity, so that would be like a list property with 5000 items in it or two properties with 2500 items in each, etc... That is the limit you are hitting I assume. On Apr 25, 3:40 am, ZS zimon.spa...@gmail.com wrote: Anyone knows the App Engine limit? (How many indexes can I use on a single property?) -- 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: Real-Time Log Delivery Via XMPP
We would love this type of feature. We currently pull our logs every 15m and store them for analysis, but when the site is busy even that can miss entries. Two things would be nice: 1. Much Much larger log level buffers. (not talking about each log line, I mean total number of entries stored) 2. Some type of logging stream to external source -Mike On Dec 1, 12:59 pm, Stephen Johnson onepagewo...@gmail.com wrote: I'm not sure if anyone is interested in this type of capability but I had a use for it for my own debugging and monitoring purposes so I thought I'd share what I came up with especially since people seem to be losing their logs or at least they aren't showing up for a while. You can read my post atwww.professionalintellectualdevelopment.com. Stephen -- 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-appeng...@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: Suddenly getting 404 on my application
We actually saw this on one of our instances yesterday. All urls would 404 and nothing showed in the logs/dashboard. A re-deploy to a new version fixed it for us. -Mike On Oct 26, 4:49 pm, Wes westho...@gmail.com wrote: One of my site's is suddenly giving a 404 on the default version as well as the other older versions. Is anyone aware of any system issues? -- 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-appeng...@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: I can see the number of instances!
Google App Engine/1.3.8 is out... On Oct 14, 8:32 pm, nischalshetty nischalshett...@gmail.com wrote: Yayy... I can now see the number of instances my app is taking in the admin console. But, what do those columns mean and what should the optimum values be for each column? -- 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-appeng...@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: Prerelease SDK 1.3.8 is out!
+1 On Oct 6, 9:59 am, mscwd01 mscw...@gmail.com wrote: +1 On Oct 6, 10:48 am, Greg g.fawc...@gmail.com wrote: On Oct 6, 1:28 pm, Ikai Lan (Google) ikai.l+gro...@google.com wrote: - The developer who uploaded an app version can download that version's code using the appcfg.py download_app command. I'm not at all happy about this. I know how frequent plaintive I lost my code how can I get it back? messages are in this group, but the write-only nature of appengine gave me a lot of confidence that our source code is safe. Now a single password is all that stands between our competitors and our IP. Why expose ALL users to risk (and open Google to lawsuits) for the sake of a few inexperienced developers? Star this post if you agree. I guess one solution would be to make downloading optional. A setting to disable source downloading in app.yaml would be safe, because uploading a new version would destroy the existing code. Greg. -- 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-appeng...@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: Google App Python src code download
I think it is good that it is NOT possible to download the source. It is a nice security feature. -mike On Jul 27, 1:20 pm, Ikai L (Google) ika...@google.com wrote: Backups are important. Any serious developer, especially if you are running a business, will have their code in a source code repository. There is no excuse for not doing so. On Thu, Jul 22, 2010 at 11:26 PM, Cluster cluster.mas...@gmail.com wrote: of course not now i must recode it all but, i think, that googlers can make some tool for restoration, or it it too much? For example, when i log in appspot.com. Why dont i have ability to download files of app? What is the point of it? -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Ikai Lan Developer Programs Engineer, Google App Engine Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- 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-appeng...@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: Datastore is now slower than before last week's maintenance
see http://googleappengine.blogspot.com/2010/07/upcoming-datastore-downtime.html we'd like to inform developers that during the period between the two maintenance events listed above, we are expecting that Datastore performance will be impacted and applications will see higher read/ write latencies. -mike On Jul 13, 6:45 am, takeru sasaki sasaki.tak...@gmail.com wrote: Hello, I feel Datastore is now slower than before last week's maintenance. Does anyone feel like same? In my dashboard, Milliseconds/Request is now 800+ms. But it was about 400ms before the maintenance. I want to back faster by this week's maintenance. But someone said it will not back, in Twitter timeline #appengine in Japanese. What is happening now in datastore? takeru -- 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-appeng...@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: App Engine Learning Resources
If you need a good AMF layer for flash on app engine (python), check out pyamf.org -mike On Jul 2, 12:32 pm, Mzor mzor...@gmail.com wrote: Hey everyone. I've been working on a Flash project recently and previously I was using PHP as the backend for it, but recently it has started to make sense to switch over to using app engine just due to the nature of the project. The issue is, I'm finding resources for app engine to be few and far between, and the tutorials really aren't that well written, being completely honest, so I've bee fumbling around for a couple weeks and have been making next to 0 headway. What I'm looking for are just learning resources outside of the tutorials up on the Google site - books, forums, classes, other tutorials. Stuff like that that could be of use. I'm much obliged, and thanks in advance for responses. -- 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-appeng...@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: Deadline?
The ones that fail right at 10 seconds are usually due to the simultaneous dynamic request limit. Do the logs show this? Request was aborted after waiting too long to attempt to service your request because you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/kb/general.html#activerequests for more details. -mike On Jun 7, 2:20 pm, Patrick Twohig patr...@namazustudios.com wrote: I was under the impression that the deadline for requests was 30 seconds, but my app is routinely throwing deadline exceptions after 10 seconds or so. Is there a reason for this? -- Patrick H. Twohig. Namazu Studios P.O. Box 34161 San Diego, CA 92163-4161 -- 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-appeng...@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: Google app Engine Deployment: Limits 3000 Files
make sure (.*\.svn/.*) is in your app.yaml skip_files directive. Use skip_files for anything you don't need to deploy. -mike On Jun 4, 12:37 pm, jeffrey jeff...@zemericks.com wrote: If you're using one of the svn Eclipse plugins, you might be publishing the .svn directories, too. That happened to me. Not sure how I fixed it but I did... On Jun 4, 7:09 am, dwvsdv svsdv mr.myk...@gmail.com wrote: Dear all, I have the pbroblem, when I deploy my application to Google App Engine by Eclipse. They said I reach to 3000 limits. Eclipse said I have 3600 Files in project. But when I check my Project Folder, it just contains 1800 files. I don't know why there are so many files. Could anyone have this experience share me? What really files will deploy to Google App Engine? Thanks and Regards, Tam Tran -- 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-appeng...@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] Status Site latency information going away?
I noticed that the farthest back I can look today is http://code.google.com/status/appengine/detail/datastore/2008/12/08#ae-trust-detail-datastore-query-latency I assume by tomorrow that link wont work and http://code.google.com/status/appengine/detail/datastore/2008/12/09#ae-trust-detail-datastore-query-latency will start to go away. Is the latency info really going away or is that a bug? I would think you might want to keep that information around, at least so we can be nostalgic and look at days when query ran in 100ms. -Mike -- 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-appeng...@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: DeadlineExceededError on very simple query
Datastore retries happen on the datastore side now, the RPC call just
blocks.
I wish we had an option for the old way, so we could control the
retries in our code. I think this new rpc blocking retry hurts
advanced users.
-mike
On Mar 24, 3:34 pm, Vladimir Prudnikov pru...@gmail.com wrote:
Sometimes such simple query
release = Release.all().order('-pub_date').fetch(1)[0]
ends with exception DeadlineExceededError. Release has 28 records. Website
has more than 1000 pageviews daily.
Is it known(?) problem? Or I just so lucky?
--
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-appeng...@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: Session Data must be in DataStore?
The session handler can just use a single get by keyname/key to load the session, and a single put to save. If you don't have to change the session every request, then put memcache in front of it so you can save on the datastore get. -mike On Mar 18, 9:36 pm, Patrick Twohig patr...@namazustudios.com wrote: For whatever its' worth, I have HTTP Basic auth implemented in my web service and it fetches the user's account details from the datastore each time a request is made and it doesn't seem to be a huge problem. On Wed, Mar 17, 2010 at 4:41 PM, Guy Smith g...@multiniche.org wrote: “If a web application wants to store session data, then it must be stored in the DataStore rather than static variables or MemCache.” - is that correct? I understand the reasoning behind it – that separate requests in a session may go to different servers, which will not have the same values in static variables or MemCache, only the DataStore is shared between servers. But it is expensive (in developer time and DataStore writes), so I’d just like to double check. NB: I have a fair bit of session data – encoding it in the cookie is not feasible. -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Patrick H. Twohig. Namazu Studios P.O. Box 34161 San Diego, CA 92163-4161 -- 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-appeng...@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: Request processing slow today
Normally you get those errors because of the simultaneous request limitation. Check out http://code.google.com/appengine/docs/python/runtime.html#Quotas_and_Limits * An application can process around 30 active dynamic requests simultaneously. This means that an application whose average server- side request processing time is 75 milliseconds can serve up to (1000 ms/second / 75 ms/request) * 30 = 400 requests/second without incurring any additional latency. Applications that are heavily CPU- bound may incur some additional latency in long-running requests in order to make room for other apps sharing the same servers. Requests for static files are not affected by this limit. On Mar 11, 5:19 am, vivpuri v...@vivekpuri.com wrote: Requests are getting processed really slow today. Error rate for my app is way up for the past 6 hours without any significant code changes. Quite a few requests are ending up with - Request was aborted after waiting too long to attempt to service your request Anyone else facing similar issue? -- 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-appeng...@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: How reliable are the App Engine Logs?
That is a really strange way to persist and retrieve data. I think logging is fairly reliable, but I don't see any reason to do it that way when the datastore is available. -mike On Mar 10, 5:38 pm, Spines kwste...@gmail.com wrote: I'm wondering how reliable are the app engine logs? If I call Logger.info(something), and the call succeeds, will the entry definitely show up in the logs? Or might it sometimes silently fail? I have some data I have to persist with every request, but I will only read the data once, about 30 minutes later by an offsite computer. Since the datastore is optimized for read efficiency, rather than write efficiency, this makes it a bad candidate for this need. I'm wondering if simply logging the data would work. I can Logger.info() the data I need to persist with every request, and my offsite computer can download the logs every 30 minutes. -- 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-appeng...@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: Clean way to code around timeouts?
I saw this lower level way to handle Timeouts. Seems like the best way to handle it. No need to decorate or litter your code with retry stuff. http://appengine-cookbook.appspot.com/recipe/autoretry-datastore-timeouts/ --~--~-~--~~~---~--~~ 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: Server error without any log
Any response from a googler on this? We are seeing this issue also. thanks! On Sep 11, 1:00 pm, Ernesto Ferro ernestofe...@gmail.com wrote: I'm having the same issue. I've made a REALLY simple site with django 1.02 (from app engine) trying to find the problem. The only thing that this app does is return an html with render_to_response. Nothing else ant yet it fail by deadline, imports or some disk i/o operations. Does google knows about this? Because it seems like the problem it's outside the users code. Regards --~--~-~--~~~---~--~~ 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: 403 Application Over Quota Problem - Not True!
enabling billing seems to have sped things up and so far has stopped the 403's. I still think something is fishy since we had not warnings in the appspot dashboard and are way under free quotas. On Jun 22, 4:58 pm, Mike Wesner m...@konsole.net wrote: Several of our appspot instances are having this exact same issue. We are way under quota, hardly hitting the appid at all and we see 403 on static files and other things. Random 500 errors too. We are enabling billing on a few of our test instances which we hope will help, but I can't see how it will make a difference since we are so far under quota/usage rates. ANY GOOGLERS READING THIS? This is a serious issue and we get ZERO information or support from google. How can a company use this stuff when its so flakey? On Jun 22, 2:19 pm, Devel63 danstic...@gmail.com wrote: All of a sudden, my app is returning 403 application over quota whenever I do anything a bit strenuous. All of the quotas are WAY under, but things that used to work fine are now triggering this message. A guess is that the budgeting process has become much more fine- grained, and is mistakenly extrapolating from one request that may do a number of DB writes and take 10 seconds. But these are extremely rare. The app name is judysapps-qa. --~--~-~--~~~---~--~~ 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] GAE Team, How does the import cache work? How do we reduce custom django overhead?
Many app engine users are using their own django, uploaded with their app. Many of those people are also using the InstallAppengineHelperForDjango() also to make it work. Possibly related. Many people including myself have been experiencing 500 errors that show class DeadlineExceededError in them. It usually occurs for most of us in the django or django helper code before our views or 'our code' even runs, before any datastore activity happens. So my questions are: 1. How does the import cache work exactly? I have read docs but still am left with questions on how exactly it works. If we have a main.py with our main() method in it... are all the imports in that file cached? Is there a way to keep our custom django in memory? 2. Since so many people use custom django, is there any plan to provide other versions of django besides the .96 version? Would it be possibe to provide .97 and 1.0 under some other name (import django97 as django)? I have read that the provided django is always loaded in memory and thus would be faster. It would sure save us a lot of files to upload also. 3. Do you have any other advice on using custom django? any advice on the high cpu warnings I get because of (IMO lgiht) datastore usage? (when the pay service is running, will that be less of an issue?) Thanks GAE team! -Mike --~--~-~--~~~---~--~~ 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: Again *major* server errors of app engine!
I think our app was running into this issue also. We are using our own django and parts of the appengine helper patch. I would see 500 errors, deadlineexceeded but the exception is thrown in the django, helper or pyamf (in our case we use pyamf to process the requests from a flex/flash client) code which was even before any datastore operations or much else ran. The question is. How do you set it up so that django/helper are cached imports? If you import things in main.py (where our main method is) does that keep things in memory? The docs seem to be pretty light on details about how to do this. -Mike On Feb 8, 3:19 am, conman constantin.christm...@googlemail.com wrote: Davel63, are you also using appengine patch? On 8 Feb., 04:48, Devel63 danstic...@gmail.com wrote: We see the same thing, and just converted to Django. Sounds like it may be related to Django. On Feb 7, 11:09 am, johnP j...@thinkwave.com wrote: No solution - just gathering information. Looking more closely at the logs where the errors occur, the deadline exceeded pops up somewhere while loading and patching django. This started a couple days ago. Maybe it'll go away? Oh well - I'm gonna enjoy the rest of the weekend, and will come back to this on Monday. :) johnP On Feb 7, 10:59 am, conman constantin.christm...@googlemail.com wrote: Yea, I am using appengine patch too and in my logs are a lot deadline exceeded errors which result from request on very simple pages without any datastore operations. But what's the problem? I have the feeling app engine is lagging at this time of the day but that may be a oversimplification... What's your solution to that problem - or are you just igoring it? Constantin On 7 Feb., 19:37, johnP j...@thinkwave.com wrote: I saw similar issues (with a google-issued, non-customized 500 deadline exceeded error). I'm using appengine patch, and saw a large increase in zipimporter calls. It seemed like a large number of requests were reloading the entire Django environment (and maybe doing so more slowly than usual...) which resulted in periodic deadline exceeded errors on very simple pages. Sound possible? johnP On Feb 7, 9:29 am, conman constantin.christm...@googlemail.com wrote: It's happening again!! Our site is not accessible but instead showing a google 500 server error page!!! The whole day everything worked normal but in the early evening (Germany/Europe) or forenoon (PST) the serving of the site is broken again - and I definitively didn't change anything today! Yesterday at the same time of the day app engine had the exact same problem:http://groups.google.com/group/google-appengine/browse_thread/thread/... What's up with that and where can I report this error so someone at google will look into that? Regards, Constantin --~--~-~--~~~---~--~~ 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: Permanent Unique User Identifier
If you save the user it has a key, and you can get a unique string from it like this: unique_keystring = str(myUser.key()) If you just want a unique string to use as a key, you could do this: import uid unique_key = str(uuid.uuid4()) Many ways to do it. I use keystrings because with a keystring you can do db.get(keystring) or even pass a list of key strings and its fast. If you use some property you have to query. -Mike On Nov 3, 11:29 pm, yejun [EMAIL PROTECTED] wrote: Why not just let user choose a user name? On Nov 3, 10:35 pm, Ryan Lamansky [EMAIL PROTECTED] wrote: Mahmoud: The problem is that won't recognize if the user changes their email address; it'll create a new entity and the user will lose everything. yejun: I thought about that, but there's no way to automatically know that a new email address was changed from some old one. User interaction is required. This requires an additional security system to be built to verify that the user did indeed have the old email address originally. There's also a possibility that the user will start creating new content before realizing there's a problem, creating the hassle of trying to merge the accounts. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Profiling code, datastore stats
The docs mention how to profile the code, which shows function calls and things. How do you profile the datastore calls? (number of queries, read/ write, time, etc) Does anyone have some interesting ways to profile their apps? The application I have been designing seems fairly clean so far and I like the shape of our data, however I am worried about all the talk of timeouts and datastore issues. For example people saying that they can't create or delete 100 records in a 10 second request. That seems horrible. It seems like we have to treat the datastore in a very fragile way. Shouldn't the limited feature set of datastore allow us to pound on it much harder than a typical relational db like mysql? I haven't had issues on appspot with our app, but we havent been able to really test our app on it because our rich internet app needs more than 1mb files. Any code snippets or discussion about the fragile nature of datastore is welcome. -Mike --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Join us for App Engine Chat Time
This is great. Thank you for reaching out to us developers. I plan on attending these. Regarding communicating with the App Engine team...what is an appropriate way to contact someone about quotas? Specifically, my team is building a rich internet app using Adobe Flex, and even using modules we have swf files that are larger than 1mb. Is it possible to request a small tweak to our file size limit? Thank you! -Mike Wesner --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Can The Development Web Server use remote datastore ?
I am fairly confident the answer is no. The dev_appserver and the sdk you download it setup to use the two files on your hard drive for the datastore. It saves pickled objects together in one big hash using memory/disk. None of the real bigtable/datastore interface code is available as far as I know. Also, I don't think they would allow you network access to the servers anyway. :D -Mike On Sep 10, 4:29 pm, Michael [EMAIL PROTECTED] wrote: I am working on a project. My PC is getting really slow when I debug it with large amount of data. Can The Development Web Server use remote datastore ? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Any (event the slightest) idea when free account limits will be lifted and we will be able to pay for storage etc?
I second, A roadmap would be lovely. p.s. Please give us LXML for python (disable the socket parts or whatever else you dont like, but we need some XSLT solution) -Mike On Sep 10, 12:05 pm, Dado [EMAIL PROTECTED] wrote: Any (event the slightest) idea when free account limits will be lifted and we will be able to pay for storage etc? Some of us have been developing apps for GAE since the very beginning and would like to launch them for real... without the current limitations on storage, file uploads, etc. The limitations of the preview release precludes the release of many apps that, for example, need to store lot of binary content in data store. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
