Re: Recompiling of .less file triggered in prod unexpectedly

That=E2=80=99s great information. So is the solution to precompile them =
for production, or to override SRSCachingInterceptor, or something else =
altogether?

> On 24 Oct 2019, at 11:09 pm, Cezary Biernacki <[email protected]> =
wrote:
>=20
> 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.ResourceTransformerFactoryImpl#=
createCompiler).
>=20
> Cezary
>=20
>=20
> On Thu, Oct 24, 2019 at 2:57 AM JumpStart <
> [email protected]> wrote:
>=20
>> 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 =
almost
>> instantaneous.
>>=20
>> I=E2=80=99ve run a sampler over it during one of these 20+ sec =
periods and it
>> seems to be spending all its time in the Less compiler. The page is =
using
>> @Import:
>>=20
>> @Import(stylesheet =3D { "css/client.less" })
>> public class Home extends LoggedIn {
>>=20
>> I=E2=80=99m using tapestry-webresources-5.4.3.jar.
>>=20
>> 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 =
more
>> than once?
>>=20
>> Regards,
>>=20
>> Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]