@@ -11,34 +11,29 @@ USE_WEBGRAPH_BIG=${USE_WEBGRAPH_BIG:-false}
11
11
JOIN_RANKS_IN_MEMORY=${JOIN_RANKS_IN_MEMORY:- true}
12
12
13
13
14
- # number of threads and Hyperball registers
15
- # depend on the size of the machine (here EC2 instance)
16
- # ... and of the graph to be processed
17
- # => it's only an empirical value and possibly needs to be adjusted
18
- THREADS=${THREADS:- 2}
19
- HYP_REG=4
20
- # # on r4.8xlarge (244 GB)
21
- # THREADS=32
22
- # HYP_REG=4 # 4-5 for hostgraph, 10 for domain graph
23
- # # on r4.16xlarge (488 GB)
24
- # THREADS=64
25
- # HYP_REG=5 # 4-6 for hostgraph, 10 for domain graph
26
- # # on r5.12xlarge (384 GB)
27
- # THREADS=48
28
- # HYP_REG=5 # 4-6 for hostgraph, 10 for domain graph
29
- # # on x1.16xlarge (976 GB)
30
- # THREADS=64
31
- # HYP_REG=9
32
- # # on x1.32xlarge (1952 GB)
33
- # THREADS=128
34
- # HYP_REG=10
35
-
36
- # determine automatically, using java.lang.Runtime.availableProcessors()
37
- # THREADS=0
38
-
39
14
# number of registers used for Hyperball / harmonic centrality calculation
15
+ #
16
+ # The number of Hyperball registers depend on
17
+ # - the size of the machine (here EC2 instance)
18
+ # - and of the graph to be processed
19
+ # => it's an empirically determined value and
20
+ # possibly needs to be adjusted
21
+ # It can be overridden by the environment variable
22
+ # HYPERBALL_REGISTERS, see below.
23
+ HYP_REG=12
24
+ # # on r8.24.xlarge (768 GB, 96 CPUs)
25
+ # HYP_REG=10 (host-level graph, 300M nodes)
26
+ # HYP_REG=12 (domain-level graph, 130M nodes)
27
+
40
28
HYPERBALL_REGISTERS=${HYPERBALL_REGISTERS:- $HYP_REG }
41
29
30
+ # number of threads
31
+ # THREAD=0 : let the webgraph tools decide how many threads,
32
+ # given the available CPU cores, using
33
+ # java.lang.Runtime.availableProcessors()
34
+ THREADS=${THREADS:- 0}
35
+
36
+
42
37
43
38
# number of fields in vertices file(s)
44
39
# (default: 2)
0 commit comments