Closed OlivierNicole closed 1 year ago
Can you also remove /dev/null
from the run_config.json
file? Why is this needed? It is not handled by rungen
.
{ "params": "-scale 21 -edgefactor 16 -ndomains 1 /dev/null", "paramwrapper": "taskset --cpu-list 2-13" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 2 /dev/null", "paramwrapper": "taskset --cpu-list 2-13" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 4 /dev/null", "paramwrapper": "taskset --cpu-list 2-13" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 8 /dev/null", "paramwrapper": "taskset --cpu-list 2-13" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 12 /dev/null", "paramwrapper": "taskset --cpu-list 2-13" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 16 /dev/null", "paramwrapper": "taskset --cpu-list 2-13,16-27" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 20 /dev/null", "paramwrapper": "taskset --cpu-list 2-13,16-27" },
{ "params": "-scale 21 -edgefactor 16 -ndomains 24 /dev/null", "paramwrapper": "taskset --cpu-list 2-13,16-27" }
Reference:
Sorry for the delay. I removed uses of /dev/null
and replaced with the relative filename edges.data
.
Given that the disk usage issue seems resolved, I propose to go back to the original parameters for the Graph500 benchmarks, and keep only the removal of /dev/null in this PR.
Can you please rebase the PR to the latest changes in the main
branch?
Done.
LGTM!
This an attempt to temporary fix #406, although increasing available disk size would be better. The Graph500 benchmarks should now produce file that are around 250 MB, rather than 1 GB.