I know that using web server logging is a bit of a hit on performance, especially if the domlog.nsf is on the same disk controller as everything else.
But, my question is…is the hit greater when everything is logged, OR is the hit greater when many things are filtered (in the server document DomLog settings) because the server has to “decide” what to log and what not to log?
I’d be interested in some numbers if anyone can point me in the right direction.
Thanks!
Subject: DomLog and Performance
I would say where the hit starts is when the server unexpectedly crashes and on the restart you have to a consistency check. HTTP will start prior to the completion of hte consistency check, but anything trying to access the database (include new entries) will fail until the consistency check is done.
I think that is the biggest performance hit. If a domlog.nsf I know is going to be big (millions of documents) I try to it replicate to another server and archive the entries so the number of documents in the database is relatively small.
HTH – cheers – email in profile.
Subject: RE: DomLog and Performance
Yes, that would be a pretty decent size hit. Aside from that, we’ll just have to monitor the situation when we implement it.
Thanks for the reply.
Subject: DomLog and Performance
Sorry for being so late in this response. We know a bit about the HTTP task and Logging because of our Workflo!log Analyzer product. First of all Processer time ALWAYS beats disc IO so filter everything you can using the Server Document. We filter all Images right off the bat. The second issue and without a doubt the biggest performance issue with DomLog.nsf is database size. the bigger the database the greater teh load on the server (not just in disk space but in access speed).That is why we recommend using our product Workflo!Log Analyzer and set the Space Saving settings on DomLog.nsf to something like 7 days.
You can read more about it and download a free demo from http://www.wfs.com