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.

Sign up for GitHub

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

Jump to bottom

getOverlapRegionFromSubTreeLocked consume many cpu hold lock #8136

Closed
Tracked by #7897
nolouch opened this issue Apr 29, 2024 · 0 comments · Fixed by #8185
Closed
Tracked by #7897

getOverlapRegionFromSubTreeLocked consume many cpu hold lock #8136

nolouch opened this issue Apr 29, 2024 · 0 comments · Fixed by #8185
Assignees
@JmPotato
Labels
type/development The issue belongs to a development tasks

Comments

@nolouch
Copy link
Contributor

nolouch commented Apr 29, 2024

Development Task

image
cpu.out.update_sub
cpu.out.update_sub.zip
@nolouch nolouch added the type/development The issue belongs to a development tasks label Apr 29, 2024
This was referenced Apr 29, 2024
Closed
Open
@JmPotato JmPotato self-assigned this Apr 29, 2024
@nolouch nolouch mentioned this issue May 17, 2024
Merged
ti-chi-bot bot added a commit that referenced this issue May 17, 2024
@JmPotato @ti-chi-bot @HuSharp
core/region: use a separate tree to check for overlaps in the subtree (…
36a1fa2 
…#8185)

ref #7897, close #8136

Previously, removing overlapped regions in subtrees required finding overlaps for each subtree individually.
This PR introduces a separate tree specifically for checking overlaps in the subtrees, thereby reducing lookup times and improving performance.

Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Co-authored-by: Hu# <jinhao.hu@pingcap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JmPotato JmPotato

Labels
type/development The issue belongs to a development tasks
Projects
None yet
Milestone
No milestone
2 participants
@JmPotato @nolouch