Reply to thread

Message: <blockquote data-quote="RonD" data-source="post: 1223374" data-attributes="member: 117536">So far no problems (1 day) with <a href="https://forum.team-mediaportal.com/attachments/tsreader_4-2-2-35-zip.190601/" target="_blank">TsReader_4.2.2.35.zip</a>Not sure what [USER=82144]@mm1352000[/USER] is looking for, but setup ProcessMonitor to track Drive-K (HDD WD30EZRZ) during MP1.16 startup. Drive-K was idle overnight and trace shows TV-Series doing recording folder scan, finding about 15 recordings that are not in database and doing a MediaInfo scan on the files. Most of these recordings are things like local TV news that are not on <a href="http://thetvdb.com/" target="_blank">Online TV Database - An open directory of television shows for HTPC software</a> so they never get added to TV-Series. Happens everytime I  start MP, feature not a bug.ProcessMonitor (csv/zip) file has the following for about 7200 disk reads. During MP startup the initial reads are to “The Ten O'clock News on KTVU Fox 2”, all initial reads must be hitting Drive-K internal ram-cache and 1st 400 reads show Read Durations less than  0.1 millisec, then the next disk read shows Duration = 636 millisec. Assume this is 1st real HDD access and needs to spin up the HDD. After this see fast disk read times less than 0.1 millisec, and others that are 15 to 20 millisec. Assume the longer reads are seek to nearby cylinder and disk spin time. BUT also see longer read durations, up to 160 millisec, assume these are longer seeks. Attached pictures show longest 100 Disk Read Durations and a Disk Duration vs Time view. In the 2nd set if pictures I set max Time = 200 millisec to ignore long 636 millisec spin up time.  My guess is the longer Durations are long seeks to next Recording on Drive-K.A high level histogram view shows the following for the slowest 100 Read Durations160 to 92 millisec, reads 1 to 25 slowest 92 to 40 millisec, reads 26 to 50, next slowest 40 to 19 millisec, reads 51 to 75 19 to 13 millisec, reads 76 to 100, probably typical short seek spin timesIn the 80s, 90s I designed and built department and database server computers, and surprised to access, seek times over 100 millisec. But servers were using 14 inch to 8 inch drives with capacities from 470 MB to 1-2 GB. Still sort of amazing a 3.5 inch drive has 3000 GB, so maybe they are a bit slower. Fujitsu Eagle <a href="https://en.wikipedia.org/wiki/Fujitsu_Eagle" target="_blank">Fujitsu Eagle - Wikipedia</a> took 2 people to install a 470 MB drive in a rack.So not sure what to say on my Drive-K recordings, feature or bug? But on this  WD “Blue”  5400 rpm HDD, spin up seems to take 600 millisec and some drive seeks can take 100 to 160 millisec. <a href="https://www.wdc.com/products/internal-storage/wd-blue-pc-desktop-hard-drive.html#WD10EZEX" target="_blank">WD Blue Desktop | Western Digital (WD)</a></blockquote>

Verification