I was thinking that if Comskip could run at "Normal" priority instead of "Low" priority, then the run times would be faster.
Here's what I do to check the priority status:
Launch the Windows Task Manager (control-shift-escape)
Left click on the "processes" tab
Right click on the Comskip process
Hover over the "Set Priority" option
You will then see that Comskip defaults to the "Low" priority level.
I have tested priority levels before for other things, and the run times are longer with the "Low" priority verses "Normal" priority. However, if can be a benefit to run at "Low" priority if the task consumes the computer too much, severely reducing other task's performance severely. For example, if a task is consuming the computer too much, opening a web browser might take many minutes.
I ran a test with Comskip on a i-7 950 quad core, 3.06 gigs. The computer is running other things that SageTV does, transcoding video files from mpeg to AVI. So, the test is not as controlled as it would be on another similar computer with less tasks running.
The test file was from HGTV, recorded in HD. The program was 60 minutes in length and 3,704 megs in size. I did two timings, one where I manually switch the Comskip priority level from "Low" to "Normal", the other where I left the Comskip priority level at "Low". The file was a TS file, and the -t switch was not used.
The time to run Comskip at "Normal" priority was 1 hour, 14 minutes, 37 seconds.
The time to run Comskip at "Low" priority was 1 hour, 16 minutes, 37 seconds.
So, it took Comskip 2 minutes longer to run at "Low" priority, which does not turn out to be a lot longer.
I could also run the tests on another nearly identical computer without SageTV to determine what difference is made. Another test could be done on a mpeg file instead. The processing time for the TS file seems very long. I don't know if that is a typical processing time for a TS file.
I was thinking that maybe if the priority level could be increased, then the processing time would decrease, but in this case, it looks like changing the priority level isn't gong to help much. Maybe many instances of Comskip need to be run at the same time, otherwise, Comskip would never be able to keep up with the programs that are being recorded.