The only time I've ever saw a problem with this is when I was buffering log lines. That caused memory issues. With that off, I've never seen any issues at all.
Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Tuesday, December 21, 2010 2:37 PM To: [email protected] Subject: Re: Impact on Enabling API/SQL Logs in Production environment We have not seen any performance impacts on our Solaris servers with all the logs turned on (except Server Group and Full Text Index which we do not use). If you do a prstat on your server how much memory is the arserverd process using? The log options we use are: Plugin Log Level: All Log File Creation: Create Backup Maximum Log File Size: 64M ( 64,000,000 ) Buffer Logged Lines: Unchecked Log Per thread: Unchecked The cron save script is basically: #! /usr/bin/ksh cur=`date +%H%M` # Set the Script path logpath=PATH_TO_LOG_FILES savepath=PATH_TO_WHERE_FILES_SHOULD_BE_SAVED cd $logpath chmod a+r *.l* # [ -r arsql.log ] && cp arsql.log ${savepath}/arsql_${cur}.log ; [ -r arfilter.log ] && cp arfilter.log ${savepath}/arfilter_${cur}.log ; [ -r arapi.log ] && cp arapi.log ${savepath}/arapi_${cur}.log ; # You get the idea on copying the files # cd ${savepath} rm -f *${cur}.log.gz > /dev/null gzip *${cur}.log # exit 0 Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Sathish Kumar P Sent: Tuesday, December 21, 2010 1:15 PM To: [email protected] Subject: Re: Impact on Enabling API/SQL Logs in Production environment Vaibhav, Thanks again, I am exactly concerned about the memory footprint going higher where it could eventvually crash the server. Unfortunately we can't simulate in our test envionrments since the user load will not be the same. The server has high memory, but remedy 7.1 is 32 bit app and hence can't grow beyond 4G and will crash when memory footprint goes beyond 4G. Also Our environment is not load balanced it is just one server. Missi, Thanks for your inputs, I will check the "buffer logged lines" option when enabling API and SQL Logs, but will enabling logs really cause any performance impact? Want to make sure user response time and ARS Memory foorpint doesn't get impacted especially. Fred, Thanks for your inputs, i am planning something like you mentioned, but would like to know if you ran into any performance issues Regards Sathish _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
