program optimization
Having decided to clean the licensed XP, purchased with the laptop, I was unpleasantly amazed by the size of some default applications.
Of course, I admit that a game with music, video clips, and a bunch of graphic elements can take more than one hundred megabytes ... but when I see that some kind of Microsoft Money is 117MB on the hard drive ... it's not comprehensible to the mind. Where from !? I have deleted five more useful and easy programs like this one ...
after that I remembered one of my project managers ... who packed a program of 5 megabytes in fifty (sic!) megabyte installer. Since the program consisted of six applications, it simply copied all dynamic libraries six times - once for each of the programs.
I also remembered another example from another project - how we diligently observed that the size of the program being downloaded was smaller, how they created the general dynamic library, and how they all packed together later. As a result, a package of three programs weighed 3 megabytes and occupied 6 after installation.
why optimize the program? After all, the screws are getting cheaper, and the processors effortlessly cope with any task.
I think that you need to do your job well. And the desire to transform the program from a voracious sluggish monster into a nimble little animal I honor the most important virtue in our camp.
The program is written once, and then can be used by a huge number of users. If you spend an extra month on its optimization in size and speed, you can eliminate most of all brakes, and cut out unnecessary weighting things. This is where the 80-20 rule works. Namely, 20% of your code causes 80% of problems. That is, to reduce the size of the program, or to improve the speed - you do not need to shovel all the code - you just need to carefully analyze it into bottlenecks, and improve them. You look, and it will become easier to breathe in the world of software.
Of course, I admit that a game with music, video clips, and a bunch of graphic elements can take more than one hundred megabytes ... but when I see that some kind of Microsoft Money is 117MB on the hard drive ... it's not comprehensible to the mind. Where from !? I have deleted five more useful and easy programs like this one ...
after that I remembered one of my project managers ... who packed a program of 5 megabytes in fifty (sic!) megabyte installer. Since the program consisted of six applications, it simply copied all dynamic libraries six times - once for each of the programs.
I also remembered another example from another project - how we diligently observed that the size of the program being downloaded was smaller, how they created the general dynamic library, and how they all packed together later. As a result, a package of three programs weighed 3 megabytes and occupied 6 after installation.
why optimize the program? After all, the screws are getting cheaper, and the processors effortlessly cope with any task.
I think that you need to do your job well. And the desire to transform the program from a voracious sluggish monster into a nimble little animal I honor the most important virtue in our camp.
The program is written once, and then can be used by a huge number of users. If you spend an extra month on its optimization in size and speed, you can eliminate most of all brakes, and cut out unnecessary weighting things. This is where the 80-20 rule works. Namely, 20% of your code causes 80% of problems. That is, to reduce the size of the program, or to improve the speed - you do not need to shovel all the code - you just need to carefully analyze it into bottlenecks, and improve them. You look, and it will become easier to breathe in the world of software.
')
Source: https://habr.com/ru/post/30540/
All Articles