Reply to thread

Message

<blockquote data-quote="ianc" data-source="post: 933946" data-attributes="member: 63303">C: drive is 180 of 300GB free with minimal fragmentation - not SSD.Timeshit drive is 400GB of 2TB (mirrored &amp; striped). CPU use is nominal &lt;5%, physical memory is about 40% available (2GB total). &nbsp;However the log file was only about 60-70KB&nbsp; and tuning was very quick. So I stopped the service again and copied the earlier large (10mb) log file back and restarted the service.Selected a channel and.......CPU use increased to 30% and channel selection took &gt;10 seconds.&nbsp; CPU dropped back to &lt;5% once the channel was visible.Deleted the log restarted and all was quick again. &nbsp;So it appeared to be directly related to the log file size. Could portions of the logging code be doing scans?&nbsp; I don't know and I'm too incompetent to check!Then I relaised I'd seen the problem before - A virus scanner buggering up a log file writer on NT4.I told EndPoint to ignore the log file directory and the problem is now avoided.&nbsp;My question still stands though - Is there a way to reduce the verbosity of the TVServer logfie?</blockquote>

[QUOTE="ianc, post: 933946, member: 63303"] C: drive is 180 of 300GB free with minimal fragmentation - not SSD. Timeshit drive is 400GB of 2TB (mirrored & striped). CPU use is nominal <5%, physical memory is about 40% available (2GB total). However the log file was only about 60-70KB and tuning was very quick. So I stopped the service again and copied the earlier large (10mb) log file back and restarted the service. Selected a channel and....... CPU use increased to 30% and channel selection took >10 seconds. CPU dropped back to <5% once the channel was visible. Deleted the log restarted and all was quick again. So it [U]appeared [/U]to be directly related to the log file size. Could portions of the logging code be doing scans? I don't know and I'm too incompetent to check! Then I relaised I'd seen the problem before - A virus scanner buggering up a log file writer on NT4. I told EndPoint to ignore the log file directory and the problem is now avoided. My question still stands though - Is there a way to reduce the verbosity of the TVServer logfie? [/QUOTE]

Verification