Answer by eric melski · Apr 24, 2012 at 04:26 PM
Nobody's done exhaustive testing, but as a general rule of thumb you can assume:
For the most part you can figure out the total impact by adding together the impact for individual detail levels. For example, if you enable both history
and waiting
, the impact is probably between 3% and 8% total. However, that does not apply for file
combined with lookup
, since file
is a subset of lookup
; and the same is true for basic
, which is a subset of everything.
Of course, your mileage may vary, and the specific impact depends on your particular build and environment. If you are really concerned about the performance the best thing to do is to benchmark the build both with and without annotation enabled and base your decisions on that, rather than some vague estimates here.
Keep in mind too that for lookup
and registry
annotation, a significant part of the performance impact comes from the cost of writing so much annotation to disk. lookup
in particular can easily cause annotation files to run to a gigabyte or more, so make sure the disk storing the annotation file is able to keep up, or you may face additional performance penalties.
CM build time longer that time in anno file 1 Answer
What is a directory lookup in anno file (rather than a read)? 2 Answers
Is compression more costly than it's worth on a 10Gb/s network? 1 Answer
Any reason to limit ElectricAccelerator max agents for a build class? 1 Answer
Is ElectricAccelerator parser performance influenced more by the emake host or by the agent host? 1 Answer
Electric Cloud powers Continuous Delivery, helping organizations developing deliver better software faster by automating and accelerating build, test, and deployment processes at scale. Industry leaders like Qualcomm, SpaceX, Cisco, GE, Gap, and E*TRADE use Electric Cloud solutions to boost DevOps productivity and Agile throughput.