Setup question

[David Becht]

When showanalyzer is processing files, my system gets very slow and my extender stops responding. I have looked at the cpu usage and it is running at 100%. I am trying the Process Lasso solution that is referred to in another post but I was wondering if their is another way to tackle the problem. Is there a way to process the files over night instead of while the programs are being recorded? I realize that some programs may not be processed before they are watched but it will not kill my system during prime time viewing. Any thoughts???

[davidk21770]

Have you tried setting analyzer priority to background?

(CPU @100% is not a bad thing IF your other tasks are getting serviced 1st -- you want show analyzer to get everything that's left after your important jobs get what they need).

[David Becht]

It is setup as a background task. However, when running, playback of recorded shows gets choppy on my main system and my media center extender gets non responsive. It doesn't seem to let the other services go first.

[davidk21770]

It could also be disk-bound -- SA using enough of the disk bandwidth that playback becomes choppy because playback can't get access to the disk when it needs it. I had that problem with one of my drives if I was recording and playing back from the same drive -- without SA. I replaced that drive...

But, the SA beta used to have a setting to throttle it's disk i/o. I don't see that in this version. Have you had any luck with process lasso?

If not, you could try an alternative directory watcher. Several have been mentioned in other threads that may do the trick for you to run SA when your system is not in use. I don't use them, so I can't comment there.

[alton987]

Originally Posted by David Becht

It is setup as a background task. However, when running, playback of recorded shows gets choppy on my main system and my media center extender gets non responsive. It doesn't seem to let the other services go first.

I don't think its disk IO. When this happens if i go and set the afftiny to 1 instead of both my cores the issue goes away. I can set it to scan 3 shows with one core and it acts fine. Its only when it starts maxing out the CPU that I will have issues.

[toricred]

The disk throttling is still there. It is on the last tab of the configurations. There is a setting for all drives combined and one for each drive separately. I've used this extensively.

It may not be the problem for everybody, but it was certainly an issue for me in the early versions of SAV1 so I've kept it configured to a combined total of 30 and individual of 15.