> So my question is, should I be concerned at the high CPU warnings or
> is it something most people experience?
i am getting similar CPU times and very similar elapsed times as u.
but i get large variation in my CPU times for no apparent reason
( same query, params).
i am using 'Always-on' so i
So how do you ensure latency is kept low? And what is considered a
high latency?
On Mar 11, 1:58 pm, Robert Kluin wrote:
> If you keep latency low you'll get new instances. Those warnings are
> left over from previous quotas and limits. You can search the groups
> for more info about it.
>
> Ro
lp,
If you haven't already, you might want to use Appstats to verify
that the variations are not actually caused by RPC calls.
Always on doesn't mean you'll never get a loading request; instances
have to be started, which will be a loading request. If you get
enough traffic to need additional
There are a couple of things you can still do:
- Try always to send high expensive operations to the background (task
queues). And also an expensive operation does not mean a lot of processing
time in your side. If you notice your API CPU usage is high, this could be a
delete/put opera
