Summary
This article contains helpful information to collect when analyzing/troubleshooting ElectricAccelerator builds.
ElectricInsight provides useful reports that you can used to analyze build performance issues and/or troubleshoot problems.
Solution
| Report | Description |
|---|---|
| ElectricSimulator | Use performance information from this build to predict approximate performance on a variety of cluster sizes. This requires –emake-annodetail=basic,waiting. |
| Files modified multiple times | Show files that were modified (created, rewritten, or deleted) multiple times. This requires –emake-annodetail=basic,file. |
| Longest serial chain | Find the sequence of serialized jobs with the longest end-to-end runtime in the build. This requires –emake-annodetail=basic,waiting,history. |
| Serialization analysis | Find the explicit and implicit dependencies that cause serialization of any two jobs in the build. This requires –emake-annodetail=basic,waiting,history. |
When troubleshooting problems related to missing targets or input files, it is very helpful to use –emake-annodetail=basic,file,lookup.
When file/network corruption is suspected during a build, using –emake-annodetail=md5 will generate md5 checksums of files that are read/written during the build.
Available –emake-annodetail options
| basic | Basic annotation |
| env | Extended environment tracking |
| file | Files read or written |
| history | Serialization details |
| lookup | All file names accessed |
| md5 | MD5 checksums for reads/writes |
| registry | Registry updates (Windows only) |
| waiting | Complete dependency graph |
Applies to
- Product versions: ElectricInsight, ElectricAccelerator
0 Comments