![]() ![]() Algorithm tuning - Every data filtering, processing, and aggregation algorithm is carefully scrutinized to maximize speed.Īlthough this isn't terribly specific (grin), my point is that the performance and stability characteristics of BP FolderSizes are rooted in sound programming practices.Stress testing / profiling - FolderSizes is tested under the most extreme environmental conditions and evaluated with sophisticated profiling tools.Thread management - Threads are managed carefully to avoid context switches and maximize user interface responsiveness.Less memory consumption means less paging, which means greater speed. ![]() Memory tuning - Great care is taken with regard to memory allocation.Native code - BP FolderSizes is developed in high-performance C++, compiled down to native machine code.Well, obviously I can't give away all my tricks, but I can to touch upon the basics. 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. I also personally guarantee that your feedback makes a difference. So again, please don't hesitate to contact me with your thoughts, even if it's just to describe how you use BulletProof FolderSizes, and I'll do my best to respond in a timely manner. In this regard, I consider BulletProof FolderSizes to be a collaboration between myself and its users, and I am very committed to that process. I've received a tremendous amount of input from the user community, in a wide variety of forms, and every bit of it (from defect reports to feature requests) is carefully scrutinized, classified, and prioritized. So let me just briefly re-iterate a basic fact about the development processes behind BulletProof FolderSizes - they are entirely customer driven. I find this state of affairs somewhat absurd, since without its user base, a software product is essentially without value. Generally when those using BulletProof FolderSizes contact me with suggestions, ideas, or a note about some unexpected behavior, they express surprise when I respond to them. An interesting trend that I've noticed in the area of software development is that most users generally expect their product feedback (including bug reports) to be ignored when they send it to developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |