On Mon, Jun 29, 2015 at 12:55 PM, Adam Pritchard <[email protected]>
wrote:
> On Friday we rolled out a test of using Caja on a small-ish set of the
> site(s) we serve. We had pre-cajoled the content (1 req/15 mins), and were
> using caja.appspot.com/caja.js to put the content into the page. Shortly
> thereafter, caja.appspot.com started returning 503, with "exceeded quota".
>
> Maybe it was us that pushed it over quota (with ~50 page hits/min), maybe
> it wasn't, but it raises the question: Should we not being using
> caja.appspot.com in a production environment? (Our full production load
> is ~50 page hits/sec.)
>
Please do not use caja.appspot.com for other than local testing purposes.
Since modern Caja is purely client-side, all that is needed is to serve the
JS files yourself.
> (I had assumed the GAE instance would have some solid Google scaling
> behind it, but apparently not.
>
caja.appspot.com is on free GAE quota. It's not meant for production use
but as a prototyping and debugging tool.
> I also assumed that, since we were pre-cajoling, that we'd only be
> retrieving static JS files. But the correctness of these assumptions is
> probably tangential.)
>
You should not be cajoling at all. The mode that uses the cajoler ("ES5/3
mode") is deprecated and slated for removal as soon as key users are fully
migrated away.
--
---
You received this message because you are subscribed to the Google Groups
"Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
