https://www.fileseek.ca/Discussions/RSS/?TopicID=b4b66783-da2b-4220-97f9-5c7962d739d5 FileSeek RSS: Performance issues Wed, 13 May 2026 16:37:15 GMT en hourly 1 https://www.fileseek.ca/Discussions/RSS/?TopicID=b4b66783-da2b-4220-97f9-5c7962d739d5 https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5#3 Fri, 22 Mar 2013 15:46:03 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5#3 FileSeek FileSeek 3.0 Beta 1 (http://www.fileseek.ca/Download/Beta/) is now available, and we've added multi-threading and done some other optimizations where possible. Hopefully it will help the performance on your setup as well!

Thanks! ]]> https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5#2 Wed, 14 Sep 2011 17:41:39 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5#2 FileSeek Thanks for doing the performance testing! That info is definitely helpful and much appreciated.

There may not be much of a way to increase the disk performance, as the 70MB/s would be based around a large continuous file transfer as opposed to tens of thousands of small reads that require more overhead. We'll still look into it though as we always like to take the opportunity to increase performance.

We'll definitely look into the CPU performance as well to see if there's a way we can improve it.

I'll be sure to let you know if we need anything tested, as it sounds like your disk structure is a good way to stress the program

Thanks! ]]> https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5 Mon, 12 Sep 2011 20:39:06 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/performance-issues/?ID=b4b66783-da2b-4220-97f9-5c7962d739d5 FileSeek Overall, FileSeek looks like a pretty slick tool. However, I do have two performance related questions/suggestions. My D: disk has 40,000 subdirectories. It takes FileSeek ~1minute (with an empty query) to find all files "foo.*". However, the Windows command 'DIR /S foo.*" only takes 5 seconds. The CPU utilization for FileSeek was 8% on a 12 CPU system (i.e. 100% on one CPU). Perhaps this is due to updating the "Current" text box? If so, perhaps updating the progress could be made an option, or done less frequently (say, 4 times a second). Also, I noticed that accessing the disk seems a little slow (3MB per second rather than the 70MB that the disk is capable of). This seems to be a semaphore related issue, as the CPU is not being maxed out either. If this code is written in Microsoft C or C++, have you considered using the *_nolock() versions of getc() etc. found in the Microsoft stdio.h file? This can increase your disk I/O performance by 4x or more. ]]>