Yeah, This is about right. It actually loads the new version of config
before releasing the existing copy. This is so the site will work until the
new config is loaded. You don't want to drop the old stuff until the new
config is validated and loaded.
It looks something like this in code.
try{
newConfig = reloadConfig();
}
...
//if all goes well
currentConfig = newConfig;
So, when reloading you will possibly need twice as much memory (more of less
depending on what mode you using and what changes you have made to the
config) for template reloading.
IMHO, 256 is probably not enough for development (of a large application).
----- Original Message -----
From: "jim moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 01, 2002 7:23 AM
Subject: Re: [Mav-user] Re: Large sites, performance issues? (jim moore)
> I can't say for sure, but knowing java garbage collection, the situation
you
> mention sounds reasonable. When mav reloads the views, it drops its
> references to the existing cached references, essentially marking them for
> garbage collection. Then it loads the new views. Now, until garbage
> collection actually collects the old views, java will essentially have two
> versions in memory, one that it is using, and one that is marked for
garbage
> collection but whose memory has not yet been freed. Possibly the time lag
> between simply loading and reloading has to do with dumping the old and
then
> loading the new--at startup it only needs to load. Jeff, does this sound
> like a reasonable explanation? Feel free to correct me.
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
[INVALID FOOTER]
