Commit d428557
Use all available CPUs to collect dump
By default, use all available CPUs to collect the dump instead of just
one CPU. This reduces the dump collection time significantly, specially
for the systems with very large memory configuration.
The graph below show the time reduction in dump collection on large
memory system from 4 Hours to 10 Minutes.
|
14000 | *
|
|
|
|
|
|
1600 | *
|
|
1400 |
execution Time (Sec) |
|
1200 |
|
|
1000 |
| *
|
800 |
|
| *
600 |
| * *
|
------------------------------------
1 9 17 25 33 41
Number of Threads
System details:
Architecture: PowerPC
/proc/vmcore size: 3.7T
Filter level: 1
Similar tests with different filter levels, 31 and 16, also show significant
reduction in time consumption for dump collection.
Although the above tests were performed only on the PowerPC architecture, but
I think using all CPUs for dump collection will have performance benefits on
other architectures too.
Note: The `--num-threads` command-line argument is added to the `makedumpfile`
core collector only when more than one processing unit is available in the
system. This helps to keep the default case (nr_cpus=1) the same.
Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>1 parent 77b80ce commit d428557
2 files changed
+12
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
147 | 147 | | |
148 | 148 | | |
149 | 149 | | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
150 | 154 | | |
151 | 155 | | |
152 | 156 | | |
| |||
384 | 388 | | |
385 | 389 | | |
386 | 390 | | |
| 391 | + | |
| 392 | + | |
| 393 | + | |
| 394 | + | |
| 395 | + | |
| 396 | + | |
| 397 | + | |
387 | 398 | | |
388 | 399 | | |
389 | 400 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1095 | 1095 | | |
1096 | 1096 | | |
1097 | 1097 | | |
| 1098 | + | |
1098 | 1099 | | |
1099 | 1100 | | |
1100 | 1101 | | |
| |||
0 commit comments