[google-appengine] Re: HItting query limit using Geocoding API from App Engine
how many requests are you making? the per IP limits are still pretty small... On Tuesday, December 17, 2013 5:17:50 PM UTC-5, Jeremy McLain wrote: > > This is driving me crazy. I've tried three different proxies and I am > still getting: "You have exceeded your daily request quota for this API." > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Using Google Cloud Storage for caching and sessions under PHP
While working on getting the Joomla CMS functioning on GAE, I've been learning a few things. One item I did was setting up a GAE specific memcached driver for caching and session handling. However, after doing so and digging a bit deeper, I realized that there are 2 different memcached implementations. Method 1: Shared memcached.. You can't lock sessions when updating - and since it is shared, your cached items can be evicted from memcache due to unpredictable usage by everyone else sharing the cache[a reasonable expectation]. This makes it especially bad for session handling as you can "lose" a session fairly easily. Method 2: Dedicated memcached. Solves the eviction problem - but if you only need a small amount of cache space[under 50Mb] your going to have to overpay since the minimium space you can reserve is 1G - so you pay for a lot of wasted space. The gs:// stream driver for Google Cloud Storage turns out to be an excellent option - you get file like access to the cached data - so you can lock and unlock the file. You can configure buckets to expire objects. Minimum time to live is 1 day, so it doesn't help with cache management for things that should expire in, say, an hour. But what it does do is allow cache cleaning for a website that has a sudden large spike in traffic[and thus a large number of cache files are created] - and then traffic stops for a few days. If you set your lifetime to 1 day, then you know that there is some sanity checking and cleaning of temporary files that will occur regardless of if the cached item is checked. So you can eliminate the spending time on garbage collection, and only check expiration dates for items as they are retrieved to make sure they are not stale. Plus the PHP stream driver will automatically cache any file read from google cloud storage into the GAE memcached system - and you can configure the TTL for that cache. The driver will automatically check memcached before trying to read a file from GS AND whenever a file is written to GS it automatically will delete it from memcached if it has been saved there. So by using Google Storage you get the speed of Memcached AND the dependability of Google Storage. I think I've found my session handler. :-) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Using Google Cloud Storage for caching and sessions under PHP
On 20 December 2013 17:38, Gary Mort wrote: > > Method 2: Dedicated memcached. Solves the eviction problem > No it doesnt. Cache can still be cleared at any time. Say instances are moved to a new data-center. But it is less likely. > > > So by using Google Storage you get the speed of Memcached AND the > dependability of Google Storage. > Yes. That's good way. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Using Google Cloud Storage for caching and sessions under PHP
On Friday, December 20, 2013 12:54:06 PM UTC-5, barryhunter wrote: > > > > > On 20 December 2013 17:38, Gary Mort >wrote: > >> >> >> > So by using Google Storage you get the speed of Memcached AND the >> dependability of Google Storage. >> > > Yes. That's good way. > > I was planning on using Datastore to store my session data and using shared Memcached to speed up lookups. But since Google built the functionality into the PHP stream handler, it just doesn't make a lot of sense to do so. Especially since there seem to be some problems with using the Datastore that way[the SDK emulates Google Storage using the Datastore but for some reason it is not able to retrieve the data it stores there. ] -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Cloud SQL quadruple billing on idling IP address?
I realise that considering the cost, this is a very minor nit - but the billing for idling IP addresses seems...odd. For my test google app, overnumerousness-site I was seeing some very odd usage charts. My Cloud SQL instance seemed to be constantly running, despite there not being any traffic. Checking the database usage for the past day, I saw an extremely small read/write blip occuring approximately every 15 minutes. Checking my GAE instance log files, I see that about every 15-16 minutes there is a single request for /index.php from my own ip address. Turns out there is a polling script on the page by default that runs to keep my session alive since I had a config screen open in the browser. This means for the last day[and during some other days], my app usage when idling is: 10 minutes of idling, Cloud SQL and GAE Instance turn off. 5 minutes later, the browser requests index.php. Cloud SQL and GAE turn back on. 10 minutes of idling, Cloud SQL and GAE instance turn off. 5 minutes later, the browser requests index.php. Cloud SQL and GAE turn back on. That amounts to roughly 40 minutes out of every hour where the Cloud SQL instance is active, which seems to match the jump in hours I noticed from yesterday to today because it wasn't quite a full X hours from when I was last working on it[around 9PM yesterday]. However, what is odd is that there seems to be a massive jump on the idling ip address hours... It seems that instead of measuring elapsed clock time, it measures each occurence. So over the course of an hour, there will be four 5 minute "idling" gaps - and for each of those occurrences it charges a full hour - so I'm paying for 4 hours of ip idling which really only took 20 minutes? It's a very small nit since it really is my own fault for not releasing the ip address when I finished working at 9pm last night[and for not closing the windows running the keep alives!] but I figured I'd mention it in case anyone else is seeing thing...it was driving me crazy trying to figure out how I was simultaneously wracking up hours of cloud sql time AND ip idling time when no one was even accessing the application. :-) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Cloud SQL quadruple billing on idling IP address?
On Friday, December 20, 2013 2:19:50 PM UTC-5, Gary Mort wrote: > > I realise that considering the cost, this is a very minor nit - but the > billing for idling IP addresses seems...odd. > > For my test google app, overnumerousness-site I was seeing some very odd > usage charts. My Cloud SQL instance seemed to be constantly running, > despite there not being any traffic. > > Checking the database usage for the past day, I saw an extremely small > read/write blip occuring approximately every 15 minutes. Checking my GAE > instance log files, I see that about every 15-16 minutes there is a single > request for /index.php from my own ip address. Turns out there is a > polling script on the page by default that runs to keep my session alive > since I had a config screen open in the browser. This means for the last > day[and during some other days], my app usage when idling is: > 10 minutes of idling, Cloud SQL and GAE Instance turn off. > 5 minutes later, the browser requests index.php. Cloud SQL and GAE turn > back on. > 10 minutes of idling, Cloud SQL and GAE instance turn off. > 5 minutes later, the browser requests index.php. Cloud SQL and GAE turn > back on. > > That amounts to roughly 40 minutes out of every hour where the Cloud SQL > instance is active, which seems to match the jump in hours I noticed from > yesterday to today because it wasn't quite a full X hours from when I was > last working on it[around 9PM yesterday]. > > However, what is odd is that there seems to be a massive jump on the > idling ip address hours... It seems that instead of measuring elapsed > clock time, it measures each occurence. So over the course of an hour, > there will be four 5 minute "idling" gaps - and for each of those > occurrences it charges a full hour - so I'm paying for 4 hours of ip idling > which really only took 20 minutes? > > It's a very small nit since it really is my own fault for not releasing > the ip address when I finished working at 9pm last night[and for not > closing the windows running the keep alives!] but I figured I'd mention it > in case anyone else is seeing thing...it was driving me crazy trying to > figure out how I was simultaneously wracking up hours of cloud sql time AND > ip idling time when no one was even accessing the application. :-) > As a sidenote, I changed my billing plan from per use to per day since while testing I'm going to be using it erratically anyway - per day seems a better choice. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Issue with Cloud Storage GCS API on local Development Server
On Tuesday, November 19, 2013 3:57:09 PM UTC-5, k...@form-runner.com wrote: > > I've encountered a problem using the Google Cloud Storage GCS Client API, > running on the local development server. I'm trying to write the bytes > from a PDF file, and then read them back. > > The code appears to write the (local fake)GCS file ok: (1) There appears > to be an appropriate entry in the Development Console, and (2) there's a > physical file in ~war/WEB-APP/appengine-generated (details below). > However, when I attempt to read the bytes from the GCS file, it throws a > FileNotFound exception when it attempts to get the metadata (filesize).\\ > I have the same problem with 1.8.8 using PHP. I can go to http://localhost:8000 and see that there are a bunch of datastore items being created from the PHP calls to save data to a file[and I can even see that the filenames in datastore match the ones that should have been created]. However, any subsequent attempts to stat those files results in a file not found error[ie check the filesize, check to see if the file exists, etc]. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Paid app e-mail quota 100 of 100, but not automatically raised?
We're using 150. Opened up the application from a small testing group to an internal beta. Our quota was raised to 1.7 Million API Calls to 20K non-admin recipients. I'm not sure why there is a manual cap on email but not anything else, and why the cap is only moved in increments, not just opened. That would be a question for the GAE team... On Friday, December 20, 2013 1:43:26 AM UTC-6, Erik Zivkovic wrote: > > On Thursday, December 19, 2013 8:25:41 PM UTC+1, Chad Vincent wrote: >> >> It took about 5-6 days for the request to clear when I asked. We knew it >> would be an issue in the long run, so we asked while still in beta. We're >> at about 150 right now. >> >> The other option is to use an external mail relay. I think there's one >> Google has a partnership with for discounted rates. >> >> On Thursday, December 19, 2013 4:57:38 AM UTC-6, Erik Zivkovic wrote: >>> >>> >>> >>> On Wednesday, December 18, 2013 9:04:16 PM UTC+1, Chad Vincent wrote: The Email quota is not automatically raised to prevent spammers from using GAE as a relay. You have to manually request that the quota be raised. On Tuesday, December 17, 2013 6:34:33 AM UTC-6, erik.z...@sonymobile.com wrote: > > Hi, > > My app has hit it's e-mail quota 100/100 e-mails, but I have an paid > app and it should be raised automatically, right? > > Users can't verify their e-mails until the quota is raised, what am I > doing wrong in my configuration? > > BR Erik > >>> I have done that, but it was three days ago, and we have 4000+ users >>> waiting to start using the service but only 100 per day can get in... >>> >>> Not all of them are registering at once, but we have hit the quota every >>> day since launch, which isn't good for us. >>> >> > Do you mean that you're using 150, or that your daily max quota is 150? > > What's the point of having differentiated pricing (cost per 100 mails) > when you can't even use as much as you want. I get the whole > anti-mail-spammer thing, but in practice GAE could be used for any > malicious acitivity, and in that case why are we allowed to use one > resource (at cost) but not another? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: App Engine credit for startups disappeared
I actually just signed up for GCE/GAE credits in the last week or so. This is what was in the email > We have successfully applied a $1,000 credit to your Google App Engine > account > and a $1,000 creditto your Google Compute Engine account. You may not see > the credit in your accounts, but it will be applied to your monthly > statements (meaning you won’t be billed until the credit in each account > is exhausted). Your credits are valid for the next six months I also can confirm that there is nothing visible in the billing or transaction area. On Thursday, December 19, 2013 2:24:29 PM UTC+11, Tomas Adamek wrote: > > Hi there > > I'm wondering if this happened to someone else as well - I've received $1k > credit for my project ~3 months ago and today I've found out it disappeared > from my transaction history - I can see the comment on previous statement > and would be expecting the amount would be credited again on next bill but > that hasn't happened so I'm bit confused now. > > App Engine Migration credit adjustment - to be applied on next bill: > USD > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] App Engine credit for startups disappeared
hi Tomas (et al), I asked the Billing team if they could shed some light, and they replied with this info: """ Due to our system migration, we had a line showing as "Migration credit adjustment" on customer's billing transaction history. But you will not actually be charged that amount - it will be automatically deducted from your monthly bill at the end of every month until the amount showing for that entry has been cleared. So please don't worry about this "Migration credit adjustment" entry. You will only be charged for resources you really used. """ So, it sounds like it will sort itself out in the invoices and you'll be charged as you expect. If it does not, this is the link for billing-related queries and issues: https://support.google.com/code/contact/cloud_platform_billing?hl=en&rd=1 -Amy On 19 December 2013 14:24, Tomas Adamek wrote: > Hi there > > I'm wondering if this happened to someone else as well - I've received $1k > credit for my project ~3 months ago and today I've found out it disappeared > from my transaction history - I can see the comment on previous statement > and would be expecting the amount would be credited again on next bill but > that hasn't happened so I'm bit confused now. > > App Engine Migration credit adjustment - to be applied on next bill: > USD > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
