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

Resolve SSW-312 (has_expected_pool_value traverses output value just once) #52

Merged

Conversation

ignaciodopazo
Copy link
Collaborator

Benchmarking:

  • original version 34 => { cpu: 5238830255, mem: 13459313 },
    35 => { cpu: 5367257843, mem: 13789894 }

  • optimized version 34 => { cpu: 5222871729, mem: 13414480 },
    35 => { cpu: 5356877915, mem: 13757945 }

Savings:

  • for 34 orders: 15.958.526 cpu and 44.833 mem
  • for 35 orders: 10.379.928 cpu and 31.949 mem

Benchmarking:
- original version
34 => { cpu: 5238830255, mem: 13459313 },
35 => { cpu: 5367257843, mem: 13789894 }

- optimized version
34 => { cpu: 5222871729, mem: 13414480 },
35 => { cpu: 5356877915, mem: 13757945 }

Savings:
- for 34 orders: 15.958.526 cpu and 44.833 mem
- for 35 orders: 10.379.928 cpu and 31.949 mem
@francolq francolq changed the title has_expected_pool_value traverses output value just once Resolve SSW-312 (has_expected_pool_value traverses output value just once) Mar 4, 2024
@francolq
Copy link
Collaborator

francolq commented Mar 4, 2024

I renamed this PR to show that it resolves SSW-312

@Quantumplation Quantumplation merged commit bfe8e8f into main Mar 5, 2024
1 check passed
@Quantumplation Quantumplation deleted the ignaciodopazo/has_expected_pool_value-optimization branch March 5, 2024 21:28
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.

3 participants