Author Topic: Unclear behaviour ...  (Read 7894 times)

kpl1949

  • Jr. Member
  • **
  • Posts: 2
    • View Profile
Unclear behaviour ...
« on: November 14, 2010, 18:55:26 »
I have a premium subscription. My audio files are located on a Gigabit NAS device, appr. 150 GB MP3 & FLAC files. PC: Intel Dual Core, 64 Bit Win7, 8 GB RAM, 1 TB HD. Problem: When terminating an analysis which ran overnight for example (duplicates or analysis) then sometimes there is a window which reports that results are saved, and other times, the program simply terminates.  When there is a window reporting that results are stored there is no information about the current status of saving. It takes 5 minutes, 10 minutes, 20 minutes .... and I still do no not know, how long it will last: another 5, 10 , 20 minutes or even hours ??? Then I kill "saving results" - because I want to shut down the  computer or use it for other actions. Next time Similarity starts from scratch (nothing has been saved) or it reports that cache cannot be read ... It would be very helpful if there is a windows which shows the percentage of already saved results so I can estimate how long it will take to finish saving. Thanks.

Admin

  • Administrator
  • Hero Member
  • *****
  • Posts: 624
    • View Profile
    • http://www.smilarityapp.com
Re: Unclear behaviour ...
« Reply #1 on: November 14, 2010, 20:56:43 »
If Similarity not stop and save after short period that means some 3rd party codec hang up on decoding, in future we add some behaviour to skip such files than saving, but this is not easy as seems, we need tests and time to implement such functional.
And in next version we add some improved loging about all functions on decoding that helps to find problematic decoders.

hsei

  • Jr. Member
  • **
  • Posts: 67
    • View Profile
Re: Unclear behaviour ...
« Reply #2 on: November 15, 2010, 13:42:15 »
I would add that short can mean a few minutes if you are working with amounts of 100k+ files. That's the time needed to save the cache of about 1GB from memory to disk. When going towards 200k files the system slows down because of excessive swapping (at 2GB RAM) and finally the system almost gets unusable because the GUI handler is swapped in and out. (It's a nostalgic feeling: It reminds me to Windows 2.0 on an IBM AT with 512 KB RAM.)