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

Perf/gkr #319

Merged
merged 213 commits into from
Feb 10, 2023
Merged

Perf/gkr #319

merged 213 commits into from
Feb 10, 2023

Conversation

Tabaie
Copy link
Contributor

@Tabaie Tabaie commented Jan 27, 2023

No description provided.

@Tabaie Tabaie marked this pull request as ready for review February 10, 2023 00:24
@Tabaie Tabaie requested a review from gbotrel February 10, 2023 00:29
@@ -44,7 +44,7 @@ type inUseData struct {

type Pool struct {
//lock sync.Mutex
inUse map[*fr.Element]inUseData
inUse sync.Map
Copy link
Collaborator

Choose a reason for hiding this comment

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

note in general about the memory pool; impact on benchmarks on my M1 laptop where negligible (vs just calling make([]fr.Element, ..))) . If it has no impact on the hpc6a instance, I'ld rather we remove this, the only piece in our codebase with unsafe import.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think its impact will increase the larger the number of instances are. Will check.

@Tabaie Tabaie merged commit 6f591e7 into develop Feb 10, 2023
@Tabaie Tabaie deleted the perf/gkr branch February 10, 2023 19:30
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.

None yet

2 participants