Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Finding bottlenecks in development system

Finding bottlenecks in development system

Scheduled Pinned Locked Moved IT & Infrastructure
performancequestionworkspace
5 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Michael S Scherotter
    wrote on last edited by
    #1

    Does anyone have any suggestions to find out what is limiting my build times: Processor, Disk, or Memory on Windows 2000? I am trying to put together configuration for development systems using MSVC 6.0 and want to know if anyone has found specific performance monitor stats are helpful. Michael S. Scherotter Lead Software Architect Tartus Development, Inc.

    M 1 Reply Last reply
    0
    • M Michael S Scherotter

      Does anyone have any suggestions to find out what is limiting my build times: Processor, Disk, or Memory on Windows 2000? I am trying to put together configuration for development systems using MSVC 6.0 and want to know if anyone has found specific performance monitor stats are helpful. Michael S. Scherotter Lead Software Architect Tartus Development, Inc.

      M Offline
      M Offline
      Maximilien
      wrote on last edited by
      #2

      There's a book called Large-Scale C++ Software Design that has a discussion on what to do to reduce build time of large projects. Besides having faster CPU, more RAM, faster HD, the user need to clean up their sources, remove useless #includes cycles, add forward declarations, change some of the structure of the classes to have "pimpl" ( private implentation ) implementations....

      M 1 Reply Last reply
      0
      • M Maximilien

        There's a book called Large-Scale C++ Software Design that has a discussion on what to do to reduce build time of large projects. Besides having faster CPU, more RAM, faster HD, the user need to clean up their sources, remove useless #includes cycles, add forward declarations, change some of the structure of the classes to have "pimpl" ( private implentation ) implementations....

        M Offline
        M Offline
        Michael S Scherotter
        wrote on last edited by
        #3

        I already have my team use that book like it were the bible. I just want to know which hardware factor is the bottleneck in my build times: Memory, Processor, or Hard drive Michael S. Scherotter Lead Software Architect Tartus Development, Inc.

        T M 2 Replies Last reply
        0
        • M Michael S Scherotter

          I already have my team use that book like it were the bible. I just want to know which hardware factor is the bottleneck in my build times: Memory, Processor, or Hard drive Michael S. Scherotter Lead Software Architect Tartus Development, Inc.

          T Offline
          T Offline
          Tim Smith
          wrote on last edited by
          #4

          Ok, it has been 8 years since I have done system tuning, so I am VERY rusty. If in task manager, you see 100% CPU usage while compiling, then CPU is the problem. Now, if you don't have enough memory, then memory has to be freed up. *ONE* way to tell this is to monitor the number of page writes or outputs per second. If you are getting a lot, then modified memory is having to be faulted out of memory. (What I don't know is how you can tell the difference between program address space faults can file cache faults.) Now, if you don't have 100% CPU usage (or around that within reason), then you might be having a disk bottleneck which can also be a low memory bottleneck causing the file cache to be purged too often. Now, a real system tuner can give you better info. I haven't tuned a system since my VMS days. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

          1 Reply Last reply
          0
          • M Michael S Scherotter

            I already have my team use that book like it were the bible. I just want to know which hardware factor is the bottleneck in my build times: Memory, Processor, or Hard drive Michael S. Scherotter Lead Software Architect Tartus Development, Inc.

            M Offline
            M Offline
            Maximilien
            wrote on last edited by
            #5

            We found that memory is at some point the bottleneck; at link time, the process takes a huge amount of memory, more than we used to have on our computer, and when the memory is full it starts to swap memory pages in and out! That took a long time. Increasing the memory of our machines, reduced the link time ! Max.

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups