Skip to content

In-memory engine: use stop-load-threshold for loading new regions#17747

Merged
ti-chi-bot[bot] merged 3 commits intotikv:masterfrom
SpadeA-Tang:stop-load-rather-eviction
Nov 3, 2024
Merged

In-memory engine: use stop-load-threshold for loading new regions#17747
ti-chi-bot[bot] merged 3 commits intotikv:masterfrom
SpadeA-Tang:stop-load-rather-eviction

Conversation

@SpadeA-Tang
Copy link
Member

What is changed and how it works?

Issue Number: Ref #16141

What's Changed:

use stop-load-threshold for loading new regions

Related changes

  • PR to update pingcap/docs/pingcap/docs-cn:
  • Need to cherry-pick to the release branch

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Release note

None

Signed-off-by: SpadeA-Tang <tangchenjie1210@gmail.com>
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the dco. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 31, 2024
@ti-chi-bot ti-chi-bot bot added needs-1-more-lgtm Indicates a PR needs 1 more LGTM. approved labels Oct 31, 2024
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: glorv, overvenus

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 1, 2024
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 1, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-10-31 08:29:40.699896373 +0000 UTC m=+511293.539051920: ☑️ agreed by glorv.
  • 2024-11-01 09:35:15.409349657 +0000 UTC m=+601628.248505204: ☑️ agreed by overvenus.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 3, 2024

@SpadeA-Tang: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot bot merged commit d01bd74 into tikv:master Nov 3, 2024
@ti-chi-bot ti-chi-bot bot added this to the Pool milestone Nov 3, 2024
overvenus pushed a commit to overvenus/tikv that referenced this pull request Nov 15, 2024
…kv#17747)

ref tikv#16141

use stop-load-threshold for loading new regions

Signed-off-by: SpadeA-Tang <tangchenjie1210@gmail.com>
Signed-off-by: Neil Shen <overvenus@gmail.com>
ti-chi-bot bot pushed a commit that referenced this pull request Nov 15, 2024
…17747 (#17831)

ref #16141, close #17767, ref #17767

In-memory engine: handle error when getting regions info (#17805)

ref #16141

handle error when getting regions info

Signed-off-by: SpadeA-Tang <u6748471@anu.edu.au>

---

In-memory Engine: Adjust memory settings based on available memory (#17515)

ref #16141

This commit adjusts the following in-memory-engine defaults:

* `capacity`: Now IME uses 10% of the block cache and takes an equal
  amount of memory from the system. This is based on tests showing that
  the IME rarely fills its full capacity.
* `mvcc_amplification_threshold`: Change from 100 to 10 which benefit
  common workloads like TPCc (50 warehouse), saving approximately 20%
  of unified read pool CPU usage.

Also, it addresses two security issues:

* Upgrade hashbrown from yanked 0.15.0 to 0.15.1

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory Engine: fix panic when destroy an uninitialized region (#17771)

close #17767

IME observes all peer destroy events to timely evict regions. By adding
a new peer, the old and uninitialized peer will be destroyed and IME
must not panic in this situation.

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory Engine: remove dead code and fix typos (#17763)

ref #16141

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory engine: use stop-load-threshold for loading new regions (#17747)

ref #16141

use stop-load-threshold for loading new regions

Signed-off-by: SpadeA-Tang <tangchenjie1210@gmail.com>

Signed-off-by: Neil Shen <overvenus@gmail.com>
Signed-off-by: SpadeA-Tang <u6748471@anu.edu.au>

Co-authored-by: Spade  A <71589810+SpadeA-Tang@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved dco-signoff: yes Indicates the PR's author has signed the dco. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants