Jump to content

Roofline model

Edit links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Giu.natale (talk | contribs) at 16:41, 22 June 2016 (→In-core ceilings: typo fix). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

An example of a Roofline model in its basic form. As the image shows, the curve consists of two platform-specific performance ceilings: the processor’s peak performance.and a ceiling derived from the memory bandwidth. Both axes are in logarithmic scale

The Roofline model is an intuitive visual performance model used to provide performance estimates of a given compute kernel or application running on multi-core, many-core, or accelerator processor architectures, by showing inherent hardware limitations, and potential benefit and priority of optimizations. By combining locality, bandwidth, and different parallelization paradigms into a single performance figure, the model can be an effective alternative to assess the quality of attained performance instead of using simple percent-of-peak estimates, as it provides insights on both the implementation and inherent performance limitations.

The most basic Roofline model can be visualized by plotting floating-point performance as a function of machine peak performance, machine peak bandwidth, and operational intensity. The resultant curve is effectively a performance bound under which kernel or application performance exists, and includes two platform-specific performance ceilings: a ceiling derived from the memory bandwidth and one derived from the processor’s peak performance.

Work

The work denotes the number of operations performed by a given kernel or application.[1] This metric may refer to any type of operation, from number of array points updated per second, to number of integer operations per second, to number of floating point operations per second (FLOPS), and the choice of one or another is driven by convenience. In the majority of the cases however, is expressed as FLOPS.[1][2][3][4][5]

Note that the work is a property of the given kernel or application and thus depend just partially on the platform characteristics.

Memory traffic

The memory traffic denotes the number of bytes of memory transfers incurred during the execution of the kernel or application.[1] In contrast to , is heavily dependent on the properties of the chosen platform, such as for instance the structure of the cache hierarchy.[1]

Operational intensity

The operational intensity , also referred to as arithmetic intensity,[2][6] is the ratio of the work to the memory traffic :[1]and denotes the number of operations per byte of memory traffic. When the work is expressed as FLOPS, the resulting operational intensity will be the ratio of floating point operations to total data movement (FLOPS/byte).

Naïve Roofline

Example of a naïve Roofline plot where two kernels are reported. The first has an operational intensity that is underneath the peak bandwidth ceiling, and is then memory-bound. Instead, the second has an operational intensity that is underneath the peak performance ceiling, and thus is compute-bound.

The naïve Roofline[2] is obtained by applying simple bound and bottleneck analysis.[7] In this formulation of the Roofline model, there are only two parameters: peak performance and peak bandwidth of the specific architecture; and one variable: operational intensity. The peak performance, in general expressed as GFLOPS, can be usually derived from architectural manuals, while the peak bandwidth, that references to peak DRAM bandwidth to be specific, is instead obtained via benchmarking.[1][2] The resulting plot, in general with both axes in logarithmic scale, is then derived by the following formula:[1]where is the attainable performance, is the peak performance, is the peak bandwidth and is the operational intensity. The point at which the performance saturates at the peak performance level - i.e. where the diagonal and horizontal roof meet - is defined as ridge point.[3] The ridge point offers insight on the machine's overall performance, by providing the minimum operational intensity required to be able to achieve peak performance, and by suggesting at a glance the amount of effort required by the programmer to achieve peak performance.[3]

A given kernel or application is then characterized by a point given by its operational intensity (on the x-axis). The attainable performance is then computed by drawing a vertical line that hits the Roofline curve. Hence. the kernel or application is said to be memory-bound if . Conversely, if , the computation is said to be compute-bound.[1]

Adding ceilings to the model

The naïve Roofline provides just an upper bound (the theoretical maximum) to performance. Although it can still give useful insights on the attainable performance, it does not provide a complete picture of what is actually limiting it. If for instance the considered kernel or application performs far below the Roofline, it might be useful to capture other performance ceilings, other than simple peak bandwidth and performance, to better guide the programmer on which optimization to implement, or even to assess the suitability of the architecture used with respect to the analyzed kernel or application.[2] The added ceilings impose then a limit on the attainable performance that is below the actual Roofline, and indicate that the kernel or application cannot break through anyone of these celining without first performing the associated optimization.[2][3]

The Roofline plot can be expanded upon three different aspects: communication, adding the bandwidth ceilings; computation, adding the so-called in-core ceilings; and locality, adding the locality walls.

  • An example of a Roofline model with added bandwidth ceilings. In this model, the two additional ceilings represent the absence of software prefetching and NUMA organization of memory.
    An example of a Roofline model with added bandwidth ceilings. In this model, the two additional ceilings represent the absence of software prefetching and NUMA organization of memory.
  • An example Roofline model with added in-core ceilings, where the two added ceilings represent the lack of instruction level parallelism and task level parallelism.
    An example Roofline model with added in-core ceilings, where the two added ceilings represent the lack of instruction level parallelism and task level parallelism.
  • An example Roofline model with locality walls. The wall labeled as 3 C's denotes the presence all three types of cache misses: compulsory, capacity and conflict misses. The wall labeled as 2 C's represent the presence of either compulsory and capacity or compulsory and conflict misses. The last wall denotes the presence of just compulsory misses.
    An example Roofline model with locality walls. The wall labeled as 3 C's denotes the presence all three types of cache misses: compulsory, capacity and conflict misses. The wall labeled as 2 C's represent the presence of either compulsory and capacity or compulsory and conflict misses. The last wall denotes the presence of just compulsory misses.

Bandwidth ceilings

The bandwidth ceilings are bandwidth diagonals placed below the idealized peak bandwidth diagonal. Their existence is due to the lack of some kind of memory related architectural optimization, such as cache coherence, or software optimization, such as poor exposure of concurrency (that in turn limit bandwidth usage).[2][3]

In-core ceilings

The in-core ceilings are roofline-like curve beneath the actual roofline that may be present due to the lack of some form of parallelism. These ceilings effectively limit how high performance can reach. Performance cannot exceed an in-core ceiling until the underlying lack of parallelism is expressed and exploited. The ceilings can be also derived from architectural optimization manuals other than benchmarks.[2][3]

Locality walls

If the ideal assumption that operational intensity is solely a function of the kernel is removed, and the cache topology - and therefore cache misses - is taken into account, the operational intensity clearly becomes dependent on a combination of kernel and architecture. This may result in a degradation in performance depending on the balance between the resultant operational intensity and the ridge point. Unlike "proper" ceilings, the resulting lines on the Roofline plot are vertical barriers through which operational intensity cannot pass without optimization. For this reason, they are referenced to as locality walls or operational intensity walls.[2][3]

Extension of the model

Since its introduction,[2][3] the model has been further extended to account for a broader set of metrics and hardware-related bottlenecks. Already available in literature there are extensions that take into account the impact of NUMA organization of memory,[5] of out-of-order execution,[8] of memory latencies,[8][9] and to model at a finer grain the cache hierarchy[4][8] in order to better understand what is actually limiting performance and drive the optimization process.

Also, the model has been extended to better suit specific architectures and the related characteristics, such as FPGAs.[10]

See also

References

  1. ^ a b c d e f g h Ofenbeck, G.; Steinmann, R.; Caparros, V.; Spampinato, D. G.; Püschel, M. (2014-03-01). "Applying the roofline model". 2014 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS): 76–85. doi:10.1109/ISPASS.2014.6844463.
  2. ^ a b c d e f g h i j Williams, Samuel W. (2008). Auto-tuning Performance on Multicore Computers (Ph.D.). University of California at Berkeley.
  3. ^ a b c d e f g h Williams, Samuel; Waterman, Andrew; Patterson, David (2009-04-01). "Roofline: An Insightful Visual Performance Model for Multicore Architectures". Commun. ACM. 52 (4): 65–76. doi:10.1145/1498765.1498785. ISSN 0001-0782.
  4. ^ a b Ilic, A.; Pratas, F.; Sousa, L. (2014-01-01). "Cache-aware Roofline model: Upgrading the loft". IEEE Computer Architecture Letters. 13 (1): 21–24. doi:10.1109/L-CA.2013.6. ISSN 1556-6056.
  5. ^ a b Lorenzo, Oscar G.; Pena, Tomás F.; Cabaleiro, José C.; Pichel, Juan C.; Rivera, Francisco F. (2014-03-31). "Using an extended Roofline Model to understand data and thread affinities on NUMA systems". Annals of Multicore and GPU Programming. 1 (1): 56–67. ISSN 2341-3158.
  6. ^ "Roofline Performance Model". Lawrence Berkeley National Laboratory. Retrieved 19 June 2016.
  7. ^ Kourtis, Kornilios; Goumas, Georgios; Koziris, Nectarios (2008-01-01). "Optimizing Sparse Matrix-vector Multiplication Using Index and Value Compression". Proceedings of the 5th Conference on Computing Frontiers. CF '08. New York, NY, USA: ACM: 87–96. doi:10.1145/1366230.1366244. ISBN 9781605580777.
  8. ^ a b c Cabezas, V. C.; Püschel, M. (2014-10-01). "Extending the roofline model: Bottleneck analysis with microarchitectural constraints". 2014 IEEE International Symposium on Workload Characterization (IISWC): 222–231. doi:10.1109/IISWC.2014.6983061.
  9. ^ Lorenzo, O. G.; Pena, T. F.; Cabaleiro, J. C.; Pichel, J. C.; Rivera, F. F. (2014-03-26). "3DyRM: a dynamic roofline model including memory latency information". The Journal of Supercomputing. 70 (2): 696–708. doi:10.1007/s11227-014-1163-4. ISSN 0920-8542.
  10. ^ da Silva, Bruno; Braeken, An; D'Hollander, Erik H.; Touhafi, Abdellah (2013-01-01). "Performance Modeling for FPGAs: Extending the Roofline Model with High-level Synthesis Tools". Int. J. Reconfig. Comput. 2013: 7:7–7:7. doi:10.1155/2013/428078. ISSN 1687-7195.{{cite journal}}: CS1 maint: unflagged free DOI (link)

Available Tools

Retrieved from "https://en.wikipedia.org/w/index.php?title=Roofline_model&oldid=726506860"