Re: Recompiling of .less file triggered in prod unexpectedly

--000000000000cc4fb70595a96b47
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Tapestry caches compiled files in memory using SoftReference<> so it is
possible for the garbage collector to remove them (see
org.apache.tapestry5.internal.services.assets.SRSCachingInterceptor). In
the development mode Tapestry also caches compilations in a temporary
directory, but unfortunately this mechanism is disabled in the production
mode
(see org.apache.tapestry5.internal.webresources.ResourceTransformerFactoryI=
mpl#createCompiler).

Cezary


On Thu, Oct 24, 2019 at 2:57 AM JumpStart <
[email protected]> wrote:

> I=E2=80=99m observing that after startup, and then after every 20 minutes=
 or so -
> actually, it seems to be quite variable - the first page after login will
> take 20 or more seconds to be displayed. The rest of the time it is almos=
t
> instantaneous.
>
> I=E2=80=99ve run a sampler over it during one of these 20+ sec periods an=
d it
> seems to be spending all its time in the Less compiler. The page is using
> @Import:
>
> @Import(stylesheet =3D { "css/client.less" })
> public class Home extends LoggedIn {
>
> I=E2=80=99m using tapestry-webresources-5.4.3.jar.
>
> I was expecting this to be a one-time event, on first visit to the page
> after startup. Under what circumstances would you expect it to happen mor=
e
> than once?
>
> Regards,
>
> Geoff

--000000000000cc4fb70595a96b47--