Allow projects to pay for more concurrent interactive queries

[GoogleCodeExporter]

Currently there's a hard limit on concurrent interactive queries: 20. That's 
pretty low when you have multiple customers at same time executing multiple 
(even small) interactive queries.

I propose a way to allow projects to pay for more concurrent interactive 
queries. Not all projects need to (or have money to) pay for a premium license, 
but still need more flexible quotas.

Original issue reported on code.google.com by gilberto...@gmail.com on 11 Nov 2014 at 8:58

[GoogleCodeExporter]

Hi, I'm going to leave this issue as "New", since we are considering options, 
but we don't have a plan to give at this point.

What type of use pattern do you have?  E.g. some projects have spiky usage from 
generating 30-graph dashboards, some have users doing their own ad-hoc things 
independently -- we'd like to make sure we cover people's uses.

Original comment by e...@google.com on 19 Nov 2014 at 6:42

[GoogleCodeExporter]

The "30-graph dashboards" is one of my use cases. I can handle that by making 
client and server queues, mitigating (but not solving) the problem.

I say it doesn't solve the problem because multiple users (let's say... 5) 
rendering dashboards at same time can produce long queues, increasing too much 
the response time of each dashboard - and you know, even 10 seconds means 
"forever" when the user is waiting for the request to complete. That's a 
problem for my project, since I have the same app for multiple customers 
(mutitenancy).

Original comment by gilberto...@gmail.com on 19 Nov 2014 at 6:59

[GoogleCodeExporter]

We haven't encountered this yet, but it definitely scares me as we are starting 
to scale.

Original comment by de...@derekperkins.com on 5 May 2015 at 4:36