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

feat(ring): new ring with less GC overhead #30

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

ppzqh
Copy link
Contributor

@ppzqh ppzqh commented Oct 17, 2024

What type of PR is this?

feat

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

BenchmarkNew/std-keysize_n_100000-12 513 2179976 ns/op
BenchmarkNew/new-keysize_n_100000-12 8821 142448 ns/op
BenchmarkNew/std-keysize_n_400000-12 136 8733349 ns/op
BenchmarkNew/new-keysize_n_400000-12 2772 421763 ns/op

BenchmarkDo/std-keysize_n_10000-12 80043 15823 ns/op
BenchmarkDo/new-keysize_n_10000-12 460353 2504 ns/op
BenchmarkDo/std-keysize_n_40000-12 22645 54163 ns/op
BenchmarkDo/new-keysize_n_40000-12 119898 10071 ns/op

BenchmarkGC/std-keysize_n_100000-12 484 2450414 ns/op
BenchmarkGC/new-keysize_n_100000-12 10000 113688 ns/op
BenchmarkGC/std-keysize_n_400000-12 126 9436167 ns/op
BenchmarkGC/new-keysize_n_400000-12 10000 113648 ns/op

(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

@ppzqh ppzqh force-pushed the feat-ring branch 2 times, most recently from 8614e53 to 5b297d3 Compare October 17, 2024 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant