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

Improve tests and benchmarks for insert #3700

Open
b1ron opened this issue Nov 8, 2023 · 1 comment
Open

Improve tests and benchmarks for insert #3700

b1ron opened this issue Nov 8, 2023 · 1 comment
Assignees
Labels
area/performance Issues about performance code/chore Code maintenance improvements community Issues and PRs assigned to community members

Comments

@b1ron
Copy link
Contributor

b1ron commented Nov 8, 2023

We should update/add benchmarks to test:

  • concurrent inserts into the same collection;
  • concurrent inserts into different collections.

The best way to do that is probably to make two copies of that benchmark and change them:

func BenchmarkInsertMany(b *testing.B) {

@b1ron b1ron self-assigned this Nov 8, 2023
@b1ron b1ron changed the title Investigate mongorestore issue Investigate mongorestore SQLITE_BUSY issue Nov 8, 2023
@b1ron b1ron changed the title Investigate mongorestore SQLITE_BUSY issue Investigate mongorestore SQLITE_BUSY error Nov 8, 2023
@AlekSi AlekSi transferred this issue from FerretDB/dance Nov 13, 2023
@b1ron b1ron changed the title Investigate mongorestore SQLITE_BUSY error Investigate SQLITE_BUSY error Nov 23, 2023
@AlekSi AlekSi changed the title Investigate SQLITE_BUSY error Improve benchmarks for insert Nov 23, 2023
@AlekSi AlekSi changed the title Improve benchmarks for insert Improve tests and benchmarks for insert Nov 23, 2023
@AlekSi AlekSi added not ready Issues that are not ready to be worked on; PRs that should skip CI code/chore Code maintenance improvements area/performance Issues about performance labels Nov 23, 2023
@AlekSi AlekSi assigned rumyantseva and unassigned rumyantseva Nov 27, 2023
@AlekSi AlekSi removed the not ready Issues that are not ready to be worked on; PRs that should skip CI label Dec 4, 2023
@AlekSi AlekSi self-assigned this Jan 31, 2024
@AlekSi AlekSi unassigned AlekSi and b1ron Apr 23, 2024
@AlekSi AlekSi added the community Issues and PRs assigned to community members label Apr 23, 2024
@wazir-ahmed
Copy link
Contributor

@AlekSi I'm interested in picking up this task next.

@AlekSi AlekSi self-assigned this May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance Issues about performance code/chore Code maintenance improvements community Issues and PRs assigned to community members
Projects
Status: Open
Development

Successfully merging a pull request may close this issue.

4 participants