tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: [OT] log4j to file or db -- which will be faster
Date Thu, 23 Oct 2003 12:23:31 GMT

Howdy,
System.currentTimeMillis() is good enough for the time of performance
assessment you're doing.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Prabhat Kumar (IT) [mailto:pkumar@bordersgroupinc.com]
>Sent: Wednesday, October 22, 2003 4:19 PM
>To: Tomcat Users List
>Subject: RE: [OT] log4j to file or db -- which will be faster
>
>thanks,
>
>would simple time calculations using Sytem.currentTimeMills() be a
reliable
>way to calculate durations?
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>Sent: Wednesday, October 22, 2003 4:23 PM
>To: Tomcat Users List
>Subject: RE: [OT] log4j to file or db -- which will be faster
>
>
>
>Howdy,
>I'd prefer the file usually, to avoid any transactional and
>translational overhead associated with SQL calls.  Of course, the best
>thing to do is for you to try it out and convince yourself.
>
>Yoav Shapira
>Millennium ChemInformatics
>
>
>>-----Original Message-----
>>From: Prabhat Kumar (IT) [mailto:pkumar@bordersgroupinc.com]
>>Sent: Wednesday, October 22, 2003 4:09 PM
>>To: tomcat-user@jakarta.apache.org
>>Subject: [OT] log4j to file or db -- which will be faster
>>
>>
>>I know that this is too generic a question, but we have a requirement
>to
>>log informational messages in our application about why certain
actions
>>were performed or not. We are considering using either a FileAppender
>or a
>>JDBCAppender. Which one do you think will be a faster operation under
>load?
>>I guess one way to find out would be to actually try it out, but was
>>wondering if you guys had thoughts about it.
>>
>>Thanks,
>>
>>Prabhat.
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged.  This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else.  If you are not the(an)
intended
>recipient, please immediately delete this e-mail from your computer
system
>and notify the sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message