Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

google app engine channel api limitations

I have been using Google app engine for ~2 years now and love it. I am tasked with making a game and I wanted to use GAE as the backend. From what I understand the Channels API is meant for this kind of application. I got the tic-tac-toe demo working and noticed that each client got its own channel. After reading the documentation a little closer I noticed that this is how the system is meant to be used. I then checked the quotas and limits in the docs and... was devastated. GAE will let me at a maximum create 60 new channels a minute. That means I can only have 60 new users a minute. This is so limiting that I cannot use this API.

So my questions are:

  1. Am I doing it right (1 client = 1 channel)
  2. Is the channel API the best API to use to update multiple clients about the current state of a game.
  3. It can't really be only 60!? Can I pay for more per minute?
like image 671
rp90 Avatar asked Nov 11 '11 23:11

rp90


People also ask

What are the limitations of API usage?

General quota limits In the API Console, there is a similar quota referred to as Requests per 100 seconds per user. By default, it is set to 100 requests per 100 seconds per user and can be adjusted to a maximum value of 1,000.

How do I increase my Google API limit?

Increase the quota for an APIGo to Google Cloud and sign in as a Google Workspace super administrator. Under Project, select the project you're using for the migration. Quotas. Using the checkboxes, select one or more quotas to edit, then click Edit Quotas.

How many maximum instance hours are supported by an App Engine as free daily usage quota when scaling an instance using automatic scaling type?

Automatic scaling has 28 free instance hours per day whereas basic scaling has only 9.


1 Answers

  1. Keep in mind that channel tokens do not expire for two hours. This means that if one client connects multiple times within the life of that token, you can serve that same channel token again, thus not counting as a creation.

    But otherwise, yes, you are correct; 1 channel per 1 client per 2 hours.

  2. The channel API is the best AppEngine API to use for this, currently, although some users are pushing for integrated WebSocket support.
  3. 60 is the max for paid billing. A whopping 6 per minute is the max for free apps. They say that you can request an increase for pretty much any resource, but the page they link to (and which I've linked to here) specifically talks about CPU usage and QPS.
like image 101
Jon Newmuis Avatar answered Oct 13 '22 00:10

Jon Newmuis