Figure 5 - uploaded by Vassil G Vassilev
Content may be subject to copyright.
Download
View publication
Memory Footprint of clang-, icc-and gcc-compiled ROOT Running HSimple.

Memory Footprint of clang-, icc-and gcc-compiled ROOT Running HSimple.

Source publication
Figure 2: Performance monitoring plots for ROOT's runtime_cxxmodules...
Figure 2 outlines performance improvements in the Interpreter...
Figure 4: Vectorization Scalability of GenVector::Mag() function.
Figure 5: Memory Footprint of clang-, icc-and gcc-compiled ROOT Running...
Continuous Performance Benchmarking Framework for ROOT
Preprint
Full-text available
  • Dec 2018
Foundational software libraries such as ROOT are under intense pressure to avoid software regression, including performance regressions. Continuous performance benchmarking, as a part of continuous integration and other code quality testing, is an industry best-practice to understand how the performance of a software product evolves over time. We p...
Cite
Download full-text

Context in source publication

Context 1
... this case, the improvement in C++ modules is due to multiple memory optimizations and implementation of more efficient symbol resolution at runtime. Figure 5 shows the memory footprint of the HSimple benchmark between ROOT builds from different compilers. ...

Similar publications

Figure 2. Research framework of the dynamic benchmark system for county...
Test results of residual sequence stationarity.
A Dynamic Benchmark System for Per Capita Carbon Emissions in Low-Carbon Counties of China
Article
Full-text available
  • Jan 2021
As the most basic unit of the national economy and administrative management, the low-carbon transformation of the vast counties is of great significance to China’s overall greenhouse gas emission reduction. Although the low-carbon evaluation (LCE) indicator system and benchmarks have been extensively studied, most benchmarks ignore the needs of th...
View