-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Wilfred:
My observations were made on an non-JIT Blackdown 117v3 JDK on an Intel
Linux platform. I used OptimizeIt (http://www.optimizeit.com). It is not
free, but they have a 30 day trial period. You can get it to work with
JServ if you configure JServ for manual starts and add in the OptimizeIt
startup line (it has its own main to which you pass the JServ main).
Java also has the more primitive profiler by using java -p:file (you must
compile with -g to use it). In the 1.1 JDK this just prints out time spent
in methods. In JDK 1.2 I think you can get reference and memory
information out of the call (I have not used it in 1.2).
Hope that helps.
-MA
Wilfried Geis wrote:
> -----------------------------
> Please read the FAQ!
> <http://java.apache.org/faq/>
> -----------------------------
>
> Michael Amster wrote:
>
> > on Solaris. Use profiling to see where the code is spending its time.
>
> Can you tell what kind of profiler you use?
>
> Are there any for free?
>
> Thanks in advance
> --
>
> Wilfried Geis
> ITM Research GmbH
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
