I know there is a lot of redundancy in the page building process of 2.1, but
that big difference compared to the new one is a surprise. Typically such
differences are only caused by larger number of i/o operations, which have
been eliminated (at least have tried to be) in 2.1 also. Actually, I was
expecting 2.1 to be still slightly faster as it caches both the results of
module loadings and template searches while the initial version of the new
Resolver doesn't yet cache its results.
Just to make sure, have you set the module.cache property to true in TR
(default is false)? The caching of module loaders and template searches in
2.1 is controlled by that property; 2.2 ModuleLoader caches always and 2.2
Resolver doesn't use a cache yet.
-- Ilkka
----- Original Message -----
From: "Kurt Schrader" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 17, 2001 07:48
Subject: Re: Updated Turbine 3.0 TDK Benchmarks
>
> On Monday, July 16, 2001, at 09:34 PM, fanyun wrote:
>
> > Can you tell us which kind of machine do you do the test.
> >
>
> Mac OS X, 500MHz G4, Apple JDK 1.3.1 Beta
>
> I have a Linux box and a Wintel Box that I could grab some
> comparative benchmarks on tomorrow if people are
> interested in that sort of thing.
>
> -Kurt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
