Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add parallel binary edge list shuffler script #67

Merged
merged 1 commit into from
Apr 22, 2024
Merged

Conversation

meyerzinn
Copy link
Collaborator

Test this script with an edge list file:

$ cat graph.el | tr '\t ' '\n' | perl -pe '$_=pack"Q",$_' > graph.bel
$ ./shufbel -rseed 1 graph.bel graph_s1.bel
$ md5sum graph_s1.bel
<some hash gets printed>
$ rm graph_s1.bel
$ ./shufbel -rseed 1 graph.bel graph_s1.bel
$ md5sum graph_s1.bel
<the same hash gets printed>

I also checked that the triangle count did not change on rmat14 vs lonestar triangle counting, which isn't conclusive proof that the edge list is the same but is pretty strong evidence.

@meyerzinn meyerzinn merged commit e4c0ac3 into main Apr 22, 2024
3 checks passed
@meyerzinn meyerzinn deleted the meyer/shufbel branch April 22, 2024 02:22
Comment on lines +101 to +102
// spawn a goroutine for every page, since each page can fault
// todo (meyer): should we limit the number of concurrent goroutines?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not todo, yes. make it a input parameter, also make threads controllable by a input parameter.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

threads is already controllable.

var wg sync.WaitGroup
// spawn a goroutine for every page, since each page can fault
// todo (meyer): should we limit the number of concurrent goroutines?
for i := uint64(0); i < num_edges; i += uint64(pageSize / 16) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to also be a program input.

@AdityaAtulTewari
Copy link
Collaborator

please revert the approval was a mistake

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants