The process

Lately I've been getting quite a few inquiries from users asking about how BulletProof FolderSizes gets the level of raw speed that it does, especially when compared with other products.

Well, obviously I can't give away all my tricks, but I can to touch upon the basics.

• Native code - BP FolderSizes is developed in high-performance C++, compiled down to native machine code.


• Memory tuning - Great care is taken with regard to memory allocation. Less memory consumption means less paging, which means greater speed.


• Thread management - Threads are managed carefully to avoid context switches and maximize user interface responsiveness.


• Stress testing / profiling - FolderSizes is tested under the most extreme environmental conditions and evaluated with sophisticated profiling tools.


• Algorithm tuning - Every data filtering, processing, and aggregation algorithm is carefully scrutinized to maximize speed.

Although this isn't terribly specific (grin), my point is that the performance and stability characteristics of BP FolderSizes are rooted in sound programming practices. Sure, I've got a few cards up my sleeve - but mostly I just enjoy sweating the details. ;-)