Women in Technology

Hear us Roar

  Improving Compilation Times: A Case Study in Performance Analysis
Subject:   Treating the symptom and not the cause ...
Date:   2002-02-25 07:14:20
From:   zebziggle
"Writing Large Scale C++ Applications" has a great discussion of how programmers make fatal coding mistakes by misusing header files includes, ignoring forward declarations, etc.

Profiling the machine is a waste of time until you are sure the source code organization is as clean and efficiently laid-out as it can be.

If this hasn't been done already, I'm sure you'll get better than 30% improvement.

Main Topics Newest First

Showing messages 1 through 2 of 2.

  • Treating the symptom and not the cause ...
    2002-02-25 07:16:48  zebziggle [View]

    Sorry, the actual books title is:

    Large-Scale C++ Software Design
    by John Lakos
  • Treating the symptom and not the cause ...
    2002-03-27 15:17:23  gdmusumeci [View]

    It's very much true that significant performance improvements in the application layer can be obtained by the application of proper software engineering principles. Some of the biggest performance improvements come about by algorithmic change; after that, just writing clean code helps immensely. The second edition of System Performance Tuning touches on this a bit in Chapter 8 -- of course, a full discussion takes a book in and of itself (I am partial to Fowler's "Refactoring," the application of which becomes somewhat obvious.)

    However, we don't always have the ability to change the source code -- certainly the average software development team is not going to have the time to attempt to effect significant speedups in the compiler (as would be necessary in the case study illustrated here).

    Part of systems engineering is often having to work with what you have, even if it is inelegant and poorly written.