>>> JOSE ADRIANO BALTIERI <[EMAIL PROTECTED]> 06-Jun-00
12:39:13 PM >>>
This is just to wrap up here for anyone else following the thread.
>> char[] content=new char[FOut.size()];
> I think you meant FOut.length(), didn't you ?
Yes, I do.
>> int red=brout.read(content,0,content.length);
>> while(red!=-1)
>> {
>> //this loop should never be called but it's a good safety
measure
>> red=brout.read(content,red-1,content.length-red);
>> }
>> //now output
>> rw.write(content,0,content.length);
> Well, after doing that, it is still consuming a lot much more
>CPU than CGI-WIN.
> How do I know that ? Using NT Perfomance Monitor, running
>the servlet, see peaks of 100 % of CPU. Running the same
>transaction again, same data, via CGI-WIN, I'll have at most
>50 % of CPU (56 %, to be more accurate).
I suspect that CPU utilization is down to the IO libraries used by
your implementation of the JVM. Lower CPU utilization probaby means
slower though doesn't it?
> Unfortunatelly, against my will, I'll have to go on with CGI-WIN.
That's a shame. I'm not sure why CPU util. is a problem for you. I
wonder if you've tried different JVMs (eg: MS JVM since you're using
NT).
If others have this problem some of the things to look at are:
- how large is the file?
- is it big enough to cause a problem for the underlying file
system?
- what is the JVM?
- what is the input stream chain? are there lots of streams that may
be behaving badly?
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
