Skip to content

Improve spdb memtable performance (#298) - #299

Merged
Yuval-Ariel merged 1 commit into
mainfrom
298-improve-spdb-memtable-perf
Feb 1, 2023
Merged

Improve spdb memtable performance (#298)#299
Yuval-Ariel merged 1 commit into
mainfrom
298-improve-spdb-memtable-perf

Conversation

@ayulas

@ayulas ayulas commented Dec 18, 2022

Copy link
Copy Markdown
Contributor

review already done by @hilikspdb for that version

@ayulas ayulas linked an issue Dec 18, 2022 that may be closed by this pull request
@ayulas

ayulas commented Dec 18, 2022

Copy link
Copy Markdown
Contributor Author

@erez-speedb @Yuval-Ariel can you pls run tests

@Yuval-Ariel

Copy link
Copy Markdown
Contributor

@ayulas plz fix failed Check buck targets test

@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch from b062d89 to e5a788b Compare December 18, 2022 14:15
@ayulas

ayulas commented Dec 18, 2022

Copy link
Copy Markdown
Contributor Author

fixed

@Yuval-Ariel
Yuval-Ariel self-requested a review December 18, 2022 14:21
@mrambacher mrambacher changed the title Improve spdb memtable performnace (#298) Improve spdb memtable performance (#298) Dec 18, 2022
@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch from e5a788b to 4e31d2b Compare December 19, 2022 14:05
@ayulas

ayulas commented Dec 19, 2022

Copy link
Copy Markdown
Contributor Author

@erez-speedb , @Yuval-Ariel pls check. it is rebased on the 298

@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch 2 times, most recently from be14410 to 704ca30 Compare December 19, 2022 17:38
@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch 2 times, most recently from a6a638b to 98a49f2 Compare December 20, 2022 09:09
@Guyme
Guyme requested a review from hilikspdb January 4, 2023 11:58

@hilikspdb hilikspdb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  1. There would be a memory problem in configuration with small DRAM and large number of CF (such as XMCyber / Flink) due to the static size of the buckets of Mutexes ...
  2. we need to emphasis the fact that the user should change the number of buckets if she needs to work on a restricted memory environment.
  3. Please add comments ....

@ayulas

ayulas commented Jan 11, 2023

Copy link
Copy Markdown
Contributor Author

fixing the build issue

@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch 2 times, most recently from 01bb530 to 62efec5 Compare January 17, 2023 09:53
@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch 3 times, most recently from 2ff2ce1 to ca71de9 Compare January 31, 2023 14:17
Reduce lock access between switch writes vectors
Avoid unnecessary lock between read and writes
Decrease the writes vectors numbers
@ayulas
ayulas force-pushed the 298-improve-spdb-memtable-perf branch from ca71de9 to 8c37223 Compare February 1, 2023 15:33
@Yuval-Ariel
Yuval-Ariel merged commit 1247fca into main Feb 1, 2023
@Yuval-Ariel
Yuval-Ariel deleted the 298-improve-spdb-memtable-perf branch May 11, 2023 08: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.

Improve spdb memtable performance

3 participants