Quote:
Originally Posted by edbro
I loaded ver 330 again and let it run fully to the end. It took like a half hour. Then I reran it immediately after and it was very quick. I guess it needed to rewrite the cache with this version.
|
That was good to hear. I guess it proves the cache code is reasonably effective.
I may change the format of the cache file again for a future release. I am seeing if writing it out as a text file would be faster than the current binary format that is being used. If so it would be worth doing as it would also mean that the cache file would be human readable which is useful for debugging purposes.
Quote:
|
It did choke on one cover.jpg that ver 227 did not. It was a very large jpg. I replaced it with a smaller cover and it didn't have a problem with it again.
|
That is strange. I cannot remember there being any difference in the image handling code between the releases.
Quote:
|
So, everything is good. It was just a shock to see the first run of this version take so long.
|
I know what you mean. I have a large personal library and I always make sure I can run against that with no obvious problems before posting a release. I thought I would have noticed a dramatic slowdown if there was one, but behaviour can vary between systems so I was not certain.