2020
DOI: 10.1007/978-3-030-58475-7_18
|View full text |Cite
|
Sign up to set email alerts
|

Towards Faster Reasoners by Using Transparent Huge Pages

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
3
2
2

Relationship

4
3

Authors

Journals

citations
Cited by 9 publications
(7 citation statements)
references
References 31 publications
0
7
0
Order By: Relevance
“…We disabled the features that may affect the performance stability, such as Intel Turbo Boost [54], dynamic voltage and frequency scaling [55], C-state/P-state controls [56], and transparent huge page support [57]. The use of huge pages is usually effective in improving the performance of applications due to increased TLB reaches and reduced TLB misses [57], [58]. In HPC systems, however, it is a well-known source of degrading the performance stability; a larger page can produce more performance imbalance due to higher probability of containing data with different memory access characteristics [59]- [61].…”
Section: Discussionmentioning
confidence: 99%
“…We disabled the features that may affect the performance stability, such as Intel Turbo Boost [54], dynamic voltage and frequency scaling [55], C-state/P-state controls [56], and transparent huge page support [57]. The use of huge pages is usually effective in improving the performance of applications due to increased TLB reaches and reduced TLB misses [57], [58]. In HPC systems, however, it is a well-known source of degrading the performance stability; a larger page can produce more performance imbalance due to higher probability of containing data with different memory access characteristics [59]- [61].…”
Section: Discussionmentioning
confidence: 99%
“…Results are gathered on Linux RHEL 7 powered on kernel 3.10.0-1127.19.1.el7 with hyperthreading disabled. Transparent huge pages are set to system default (Fichte et al, 2020). We follow standard guidelines for empirical evaluations (van der Kouwe et al, 2018;Fichte et al, 2021b) and measure runtime using perf and enforce limits using runsolver (Roussel, 2011).…”
Section: Empirical Evaluationmentioning
confidence: 99%
“…We forced performance governors to 2.2 GHz clock speed [71], disabled hyper threading, and enforced the process that handles the solver invocation to run on cores 0,1,14,15 and enforced solvers to run on cores 2-6, 7-11, 14-18, and 19-23. We explicitly disabled transparent huge pages [34].…”
Section: Submission Requirements and Limitsmentioning
confidence: 99%