arjen stolk wrote:
> ----- Original Message -----
> From: "Berin Loritsch" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, December 07, 2001 4:29 PM
> Subject: Re: performance
>
>
>
>>arjen stolk wrote:
>>
>>
>>>hello all,
>>>
>>>
>>>
> well indeed memory is thight.
> but i don't here the disk scratcing like hell. according to taskmanager some
> physical mem is left all the time (anywhere between 64k and 32k)
>
>
> i am checking the logs. what is not clear to me is what to expect in which
> log.
> i guess i could look that up somewhere...
>
> ok i checked the components.log
> and this is what i found:
> (a lot of times)
>
> DEBUG (2001-12-07) 16:52.03:607 [root.sto] (Unknown-URI)
> Unknown-thread/StoreJanitorImpl: getHeapsize()=60000000
> DEBUG (2001-12-07) 16:52.03:607 [root.sto] (Unknown-URI)
> Unknown-thread/StoreJanitorImpl: getJVM().freeMemory()=3816
> 912
> DEBUG (2001-12-07) 16:52.03:607 [root.sto] (Unknown-URI)
> Unknown-thread/StoreJanitorImpl: getFreememory()=1000000
>
> i guess i can turn logging debug info off.
> but then what is wrong with the janitor?
The Janitor is used to check the Cache and the memory to remove things from
cache if necessary. You can get rid of DEBUG messages and gain an appreciable
differece in performance, however you may want to try a couple of other things
first.
Is your JVM set with the following params:
java -Xms64M -Mmx128M ?
This keeps the JVM from using more than your physical memory. Remember, it is
cheaper for your JVM to manage your memory than for your OS to cache to disk.
Also, do a search for the word Exception in the contents of the files in the log
directory (I think you said you were on windows). If you see any concerning
your database connection, that can hurt performance.
Play with your cache settings. If you have your cache set at 512M when you only
have 128M available, your cache might try to use too many resources--slowing
the garbage collection cycle.
Also, you didn't answer my first question:
Is this 45 second access only for the first time you access the page, or _every_
time you access the page. Remember that the sitemap and the XSP pages must be
compiled before they can be used. This means the XML is converted to a Java
source file, and then compiled with javac. It is not uncommon for it to take
as long as 45 seconds on a resource constrained machine (these days 450MHz and
128MB are considered small) to compile. However, after the first access the
page loads are lightening quick. Another thing to examine is if the timestamps
are being altered during regular serving. If so, the page might be compiled
every time the page is requested.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
