@cloudstack.apache.org
Subject: Re: cloudstack UI through accelerator/cache/proxy
I too use NetScaler and I actually found compression to have more of an impact
than caching. Caching probably didn't help as much due to the jQuery stuff.
On Dec 10, 2015 8:30 PM, "Nux!" <n...@li.nux.ro>
I’m trying to get a basic understanding on how much the performance of the ACS
UI would improve if it was run through some form of accelerator/reverse
proxy/cache (i.e. something like a netscaler)
Scenario is a management server that is a long way (physically) from the
users, therefore
The only thing you could cache as far as I can see is static content (js,
css, pictures) and list calls.
Anything that triggers an action has to reach the mgmt server and cannot be
cached.
When caching list calls you have to either have a really short lifespan, or
a proper method of invalidating
, interception or
interference.
-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: Thursday, 10 December 2015 1:26 PM
To: users@cloudstack.apache.org
Subject: Re: cloudstack UI through accelerator/cache/proxy
The only thing you could cache as far as I can see is static
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Giles Sirett" <giles.sir...@shapeblue.com>
> To: users@cloudstack.apache.org
> Sent: Thursday, 10 December, 2015 11:06:01
> Subject: cloudstack UI through accelerat
ent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Giles Sirett" <giles.sir...@shapeblue.com>
> > To: users@cloudstack.apache.org
> > Sent: Thursday, 10 December, 2015 11:06:01
> >
