[google-appengine] Frontend is too expensive! urgent
Hi, I dont understand frontend costs. currently (06/05) my estimated cost for this month are 24$ which are calculated for 470.23 frontend hours. as its seemd from instances graph that the avr.instance/sec are liitle more than 1. however calculating 470 hours divided by the 5 day from the start of this month gives 240/24/5 = 3.9 instances/sec this cause very high cost for the frontend. please help me to understand this cost calculation. https://lh3.googleusercontent.com/-FV8sb0u57zE/VUnW5pxnjII/AC8/7Z9LkoT9vhw/s1600/SS.png -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/818af768-639a-482a-8bc6-5da84bc1041f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Google App Engine 1.9.19 and google-api-python-client-gae-1.2
We had a similar issue with this error in our tests. We have our own (old, 1.2) versions of these libraries in our app. The new SDK seems to include its own (newer) version of libraries. This seems to cause an import conflict. We solved it for our tests by making sure our app's path is used before those of the SDK. Also, those newer versions don't run directly on App Engine, as they try to import the 'six' module. On Tuesday, May 5, 2015 at 10:06:39 PM UTC+2, PK wrote: The GAE documentation states here https://developers.google.com/api-client-library/python/start/installation that for GAE a special version of the library is needed and points to a Google Code location where the most recent version of the library is 1.2 Since then the library has migrated to github https://github.com/google/google-api-python-client and the most recent general version is 1.4 No mention for a GAE version in github. As I moved to the latest google appengine version SDK (1.9.19) I now see the following error in my dev server logs: File “….., line 8, in module from apiclient.errors import HttpError File apiclient/errors.py, line 27, in module from oauth2client.anyjson import simplejson ImportError: No module named anyjson A quick look at the latest google-api-python-client shows that this code is rewritten. I assume that the error is due to GAE moving to a new version of oauthclient2 Has anybody else faced this issue? Any workarounds? Is google-api-python-client-1.4 compatible with GAE? Thanks, PK p...@gae123.com javascript: -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9fd9e2c3-1f8a-4b3b-b9e0-a734cf30d5df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] is there a replacement for deprecated RecordReadChannel
Since recently we get a message saying: The Google Cloud Storage Java API is deprecated and will soon be removed. Please use the Google Cloud Storage Client library instead. Migration documentation is available here: https://cloud.google.com/appengine/docs/java/googlecloudstorageclient/migrate The problem is that new googlecloudstorageclient is missing some key functionality present in old api. One good feature in old api, it allows to read leveldb format via openRecordReadChannel() method, which is very helpful if we want to restore data from from appengine backups. Is there a replacement i missed? If not I would strongly urge Team@Google to port those classes too. Thanks, HG -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f0d8ce19-5b28-4d52-99ab-6a7412bf0c25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Appengine Logs and BigQuery
Hi, I am sending the Appengine Log to BigQuery using the LogViewer screen. In the BigQuery browser, I see that a table is created for every 1 day of log. Question: How can I send the logs to the same table instead of to different table every day. -Aswath www.AccountingGuru.net http://www.accountingguru.net/ www.VeersoftSolutions.com http://www.veersoftsolutions.com/ -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAKFF5G52UXBjf2PsypHMQmqn2dpmz_OFWa%2Bk%2B-pzaxx1p%2B5cEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] The future of prospective search
Hi Chris, thanks for showing leadership on the API status lingering issue. Any other APIs you would suggest we hold off from using while you go through the internal evaluation? Thanks PK p...@gae123.com On May 6, 2015, at 3:46 PM, 'Chris Ramsdale' via Google App Engine google-appengine@googlegroups.com wrote: hey Frederik, the prospective search API has been in Alpha way too long, i agree. we're currently working through options on what to do with that particular API moving forward. the functionality is very useful (IMO), but the underlying integration between the backend service (internal to Google) and Cloud Datastore is not ideal longer term. i would suggest holding off on using this API for any production workloads at this point. related, i get that there is some cruft in the overall API set; some APIs lingering in Alpha and Beta for months to years. we're in the process of looking deeply into the situation. look for an update in the next 1-2 months. -- Chris Product Manager, Google Cloud Platform On Wed, May 6, 2015 at 12:58 PM, Frederik Creemers frederikcreem...@gmail.com mailto:frederikcreem...@gmail.com wrote: Hi everyone, I am building an application, which could make great use of the prospective search feature. But the fact that it's in Alpha scares me. It's been in alpha for years, now, you could even say that it's alpha state has stabilized :). I understand that Google is focussing on Google Cloud Dataflow, Google Cloud PubSub, and other products that make processing real-time data easier, so that makes me even more scare about the fate of prospective search. What should I expect? Can I experiment with it, or am I wasting time if I do because it's going away? Can I use it in production? -- 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 mailto:google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com mailto:google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6a0815b0-6074-420e-8b7f-a61156fafa10%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/6a0815b0-6074-420e-8b7f-a61156fafa10%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. -- 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 mailto:google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com mailto:google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAD1DWLjHXjkhv8BNN8fh3Ur%3Dq4N-mgqWa-H5DMWvv5LGF%2BxVEQ%40mail.gmail.com https://groups.google.com/d/msgid/google-appengine/CAD1DWLjHXjkhv8BNN8fh3Ur%3Dq4N-mgqWa-H5DMWvv5LGF%2BxVEQ%40mail.gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/DAFC9F3D-567F-4631-AD74-7240664CD7EF%40gae123.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] The future of prospective search
hey Frederik, the prospective search API has been in Alpha way too long, i agree. we're currently working through options on what to do with that particular API moving forward. the functionality is very useful (IMO), but the underlying integration between the backend service (internal to Google) and Cloud Datastore is not ideal longer term. i would suggest holding off on using this API for any production workloads at this point. related, i get that there is some cruft in the overall API set; some APIs lingering in Alpha and Beta for months to years. we're in the process of looking deeply into the situation. look for an update in the next 1-2 months. -- Chris Product Manager, Google Cloud Platform On Wed, May 6, 2015 at 12:58 PM, Frederik Creemers frederikcreem...@gmail.com wrote: Hi everyone, I am building an application, which could make great use of the prospective search feature. But the fact that it's in Alpha scares me. It's been in alpha for years, now, you could even say that it's alpha state has stabilized :). I understand that Google is focussing on Google Cloud Dataflow, Google Cloud PubSub, and other products that make processing real-time data easier, so that makes me even more scare about the fate of prospective search. What should I expect? Can I experiment with it, or am I wasting time if I do because it's going away? Can I use it in production? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6a0815b0-6074-420e-8b7f-a61156fafa10%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/6a0815b0-6074-420e-8b7f-a61156fafa10%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAD1DWLjHXjkhv8BNN8fh3Ur%3Dq4N-mgqWa-H5DMWvv5LGF%2BxVEQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Frontend is too expensive! urgent
Thanks Patrice, my app is work on F4_G1 (now changed it to F1) what do you mean with : type of instance are you spinning up can change the way instance hours are calculated. isn't it like comparing apples to oranges - instant type and woking hours - and if instant type does matter is it documented somewhere? On Wednesday, May 6, 2015 at 10:15:10 PM UTC+3, Patrice wrote: Hi, You can read up here on that here : https://cloud.google.com/appengine/docs/quotas#Instances. I don't have access to your application, but seeing how this goes up and down very frequently, you might be hit by the fact that everytime an instance goes up, you are charged for at least 15 minutes. So all those spikes in the graph going up and down might be causing a bit more costs to you. Also, what type of instance are you spinning up? F1, F2, etc? that can change the way instance hours are calculated. Thank you On Wednesday, May 6, 2015 at 5:02:46 AM UTC-4, רון טופול wrote: Hi, I dont understand frontend costs. currently (06/05) my estimated cost for this month are 24$ which are calculated for 470.23 frontend hours. as its seemd from instances graph that the avr.instance/sec are liitle more than 1. however calculating 470 hours divided by the 5 day from the start of this month gives 240/24/5 = 3.9 instances/sec this cause very high cost for the frontend. please help me to understand this cost calculation. https://lh3.googleusercontent.com/-FV8sb0u57zE/VUnW5pxnjII/AC8/7Z9LkoT9vhw/s1600/SS.png -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/eb57042a-caf1-401d-b42a-ddfa07cc2fd8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Frontend is too expensive! urgent
Thanks Patrice, my app is work on F4_G1 (now changed it to F1) what do you mean with : type of instance are you spinning up can change the way instance hours are calculated. isn't it like comparing apples to oranges - instant type and woking hours - and if instant type does matter to working hours is it focumented somewhere? On Wednesday, May 6, 2015 at 10:15:10 PM UTC+3, Patrice wrote: Hi, You can read up here on that here : https://cloud.google.com/appengine/docs/quotas#Instances. I don't have access to your application, but seeing how this goes up and down very frequently, you might be hit by the fact that everytime an instance goes up, you are charged for at least 15 minutes. So all those spikes in the graph going up and down might be causing a bit more costs to you. Also, what type of instance are you spinning up? F1, F2, etc? that can change the way instance hours are calculated. Thank you -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f724f089-066b-4015-a8ed-a314b01fb341%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Google App Engine 1.9.19 and google-api-python-client-gae-1.2
Some new information under the section Using pip Requirements Files https://cloud.google.com/appengine/docs/python/tools/libraries27 suggests that it might now be possible to run the latest version without a special bundle needed. I will try it out…. By the way, has this new functionality been announced when it was released? Isn’t this stuff that should be in some sort of release notes? If it is and I have just missed it, please do point it out to me, maybe I am not checking all the right places. On May 6, 2015, at 1:03 AM, troberti tij...@firigames.com wrote: We had a similar issue with this error in our tests. We have our own (old, 1.2) versions of these libraries in our app. The new SDK seems to include its own (newer) version of libraries. This seems to cause an import conflict. We solved it for our tests by making sure our app's path is used before those of the SDK. Also, those newer versions don't run directly on App Engine, as they try to import the 'six' module. On Tuesday, May 5, 2015 at 10:06:39 PM UTC+2, PK wrote: The GAE documentation states here https://developers.google.com/api-client-library/python/start/installation that for GAE a special version of the library is needed and points to a Google Code location where the most recent version of the library is 1.2 Since then the library has migrated to github https://github.com/google/google-api-python-client and the most recent general version is 1.4 No mention for a GAE version in github. As I moved to the latest google appengine version SDK (1.9.19) I now see the following error in my dev server logs: File “….., line 8, in module from apiclient.errors import HttpError File apiclient/errors.py, line 27, in module from oauth2client.anyjson import simplejson ImportError: No module named anyjson A quick look at the latest google-api-python-client shows that this code is rewritten. I assume that the error is due to GAE moving to a new version of oauthclient2 Has anybody else faced this issue? Any workarounds? Is google-api-python-client-1.4 compatible with GAE? Thanks, PK p...@ gae123.com http://gae123.com/ -- 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 mailto:google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com mailto:google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9fd9e2c3-1f8a-4b3b-b9e0-a734cf30d5df%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/9fd9e2c3-1f8a-4b3b-b9e0-a734cf30d5df%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. PK p...@gae123.com -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/317AF1C8-9322-4746-8C39-585708036961%40gae123.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Channel API Hours Used quota exceeded
It looks like I am hit by this: https://code.google.com/p/googleappengine/issues/detail?id=4764 https://code.google.com/p/googleappengine/issues/detail?id=4764 A 5 years old known issue, 61 people have starred it, a very reasonable request, still comes and bites us. On May 6, 2015, at 10:11 AM, PK p...@gae123.com wrote: Thanks Jesse, I tuned my code and we will see how it goes. There seems to be an issue with some customers who keep failing to communicate over a channel and keep asking for a new channel. Other customers are fine. I still need to get to the bottom of this. Is the channel communication over ports that could be blocked by a firewall? I think the other issue here is that we need alerts when quotas reach certain thresholds because I completely missed this. The Dashboard does not show this particular quota which made things worse. Any recommendations on this would be appreciated. Best, On May 6, 2015, at 9:48 AM, Jesse Scherer (Google Cloud Support) jsche...@google.com mailto:jsche...@google.com wrote: Hi PK, The Channel API Hours Used quota has to with the TTL (time to live) of the channels you are opening. In Python, this is the duration_minutes variable, and it defaults to two hours: https://cloud.google.com/appengine/docs/python/channel/functions https://cloud.google.com/appengine/docs/python/channel/functions. Note that enabling billing for your app increases the limit 15X to 180 channel hours per minute. This would mean that every minute, you could open one channel with a TTL of 180 hours, ten channels with a TTL of 18 hours, 1800 channels with 6 minute TTLs, and so on. Beyond making sure that billing is enabled for your app, the best advice is to check that the TTL you are using makes sense. Again, this quota cares about how long of a TTL you ask for when you create the channel, not how long the channels eventually last. So, if in production you notice that channels only last a few minutes, lowering your TTL from the 2 hour default to 30 minutes would help a lot. Regards, and let us know if you're still running into problems. On Wednesday, May 6, 2015 at 12:21:21 AM UTC-4, PK wrote: For the first time ever today I get this message, in the console. The API channel.create_channel fails with an exception as a consequence. Has anybody experienced it? Is signing up for a support program the only way to have it increased? Thanks, PK p...@gae123.com mailto:p...@gae123.com -- 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 mailto:google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com mailto:google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. PK p...@gae123.com mailto:p...@gae123.com PK p...@gae123.com -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9E2A9AE3-2CDD-48AB-B607-6E95B3EC52B2%40gae123.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Frontend is too expensive! urgent
Hi, You can read up here on that here : https://cloud.google.com/appengine/docs/quotas#Instances. I don't have access to your application, but seeing how this goes up and down very frequently, you might be hit by the fact that everytime an instance goes up, you are charged for at least 15 minutes. So all those spikes in the graph going up and down might be causing a bit more costs to you. Also, what type of instance are you spinning up? F1, F2, etc? that can change the way instance hours are calculated. Thank you On Wednesday, May 6, 2015 at 5:02:46 AM UTC-4, רון טופול wrote: Hi, I dont understand frontend costs. currently (06/05) my estimated cost for this month are 24$ which are calculated for 470.23 frontend hours. as its seemd from instances graph that the avr.instance/sec are liitle more than 1. however calculating 470 hours divided by the 5 day from the start of this month gives 240/24/5 = 3.9 instances/sec this cause very high cost for the frontend. please help me to understand this cost calculation. https://lh3.googleusercontent.com/-FV8sb0u57zE/VUnW5pxnjII/AC8/7Z9LkoT9vhw/s1600/SS.png -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a0b53823-2703-4485-9c17-e60161c95194%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] The future of prospective search
Hi everyone, I am building an application, which could make great use of the prospective search feature. But the fact that it's in Alpha scares me. It's been in alpha for years, now, you could even say that it's alpha state has stabilized :). I understand that Google is focussing on Google Cloud Dataflow, Google Cloud PubSub, and other products that make processing real-time data easier, so that makes me even more scare about the fate of prospective search. What should I expect? Can I experiment with it, or am I wasting time if I do because it's going away? Can I use it in production? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6a0815b0-6074-420e-8b7f-a61156fafa10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Channel API Hours Used quota exceeded
Hi PK, The Channel API Hours Used quota has to with the TTL (time to live) of the channels you are opening. In Python, this is the duration_minutes variable, and it defaults to two hours: https://cloud.google.com/appengine/docs/python/channel/functions. Note that enabling billing for your app increases the limit 15X to 180 channel hours per minute. This would mean that every minute, you could open one channel with a TTL of 180 hours, ten channels with a TTL of 18 hours, 1800 channels with 6 minute TTLs, and so on. Beyond making sure that billing is enabled for your app, the best advice is to check that the TTL you are using makes sense. Again, this quota cares about how long of a TTL you ask for when you create the channel, not how long the channels eventually last. So, if in production you notice that channels only last a few minutes, lowering your TTL from the 2 hour default to 30 minutes would help a lot. Regards, and let us know if you're still running into problems. On Wednesday, May 6, 2015 at 12:21:21 AM UTC-4, PK wrote: For the first time ever today I get this message, in the console. The API channel.create_channel fails with an exception as a consequence. Has anybody experienced it? Is signing up for a support program the only way to have it increased? Thanks, PK p...@gae123.com -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: Channel API Hours Used quota exceeded
Thanks Jesse, I tuned my code and we will see how it goes. There seems to be an issue with some customers who keep failing to communicate over a channel and keep asking for a new channel. Other customers are fine. I still need to get to the bottom of this. Is the channel communication over ports that could be blocked by a firewall? I think the other issue here is that we need alerts when quotas reach certain thresholds because I completely missed this. The Dashboard does not show this particular quota which made things worse. Any recommendations on this would be appreciated. Best, On May 6, 2015, at 9:48 AM, Jesse Scherer (Google Cloud Support) jsche...@google.com wrote: Hi PK, The Channel API Hours Used quota has to with the TTL (time to live) of the channels you are opening. In Python, this is the duration_minutes variable, and it defaults to two hours: https://cloud.google.com/appengine/docs/python/channel/functions. Note that enabling billing for your app increases the limit 15X to 180 channel hours per minute. This would mean that every minute, you could open one channel with a TTL of 180 hours, ten channels with a TTL of 18 hours, 1800 channels with 6 minute TTLs, and so on. Beyond making sure that billing is enabled for your app, the best advice is to check that the TTL you are using makes sense. Again, this quota cares about how long of a TTL you ask for when you create the channel, not how long the channels eventually last. So, if in production you notice that channels only last a few minutes, lowering your TTL from the 2 hour default to 30 minutes would help a lot. Regards, and let us know if you're still running into problems. On Wednesday, May 6, 2015 at 12:21:21 AM UTC-4, PK wrote: For the first time ever today I get this message, in the console. The API channel.create_channel fails with an exception as a consequence. Has anybody experienced it? Is signing up for a support program the only way to have it increased? Thanks, PK p...@gae123.com mailto:p...@gae123.com -- 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 mailto:google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com mailto:google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. PK p...@gae123.com -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/554D73C9-6DFA-496A-8634-9BD22D8F7AA0%40gae123.com. For more options, visit https://groups.google.com/d/optout.
