View Single Post
Old 30th June 2020, 10:17   #29533  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,531
Quote:
When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.
An app being quicker on second run is no mystery, happens with sore more SW.
Its just that these date are still kept in RAM.
Like with tsMuxeR, muxing time went from 9..10 min first run
down to 1,5 minutes for the same 10GB test stream on second and third run.
(Magnetic platter HDDs used, with SSD maybe unnoticeable)
I just extensively tested for one particular stream losing packets at the end.
(solved since the 2020-06-27 build for me, BTW)

Would fit the available 32GB RAM. (Did not run RAMMap though to confirm)
Why it would be slower on third run, I cannot comment.
But if I close the app and allow the RAM to be flushed, then it may take the full first running time again.
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're that issue working on. Synce invntoin uf lingöage..."

Last edited by Emulgator; 30th June 2020 at 10:23.
Emulgator is offline   Reply With Quote