KVStore: Reduce lock contention in RegionPersister::doPersist (#8584)

[ti-chi-bot]

This is an automated cherry-pick of #8584

What problem does this PR solve?

Issue Number: close #8583

Problem Summary:

tiflash/dbms/src/Storages/KVStore/MultiRaft/RegionPersister.cpp

Lines 99 to 125 in 5980908

	void RegionPersister::doPersist(
	RegionCacheWriteElement & region_write_buffer,
	const RegionTaskLock & region_task_lock,
	const Region & region)
	{
	auto & [region_id, buffer, region_size, applied_index] = region_write_buffer;
	std::lock_guard lock(mutex);
	auto entry = page_reader->getPageEntry(region_id);
	if (entry.isValid() && entry.tag > applied_index)
	return;
	if (region.isPendingRemove())
	{
	LOG_DEBUG(log, "no need to persist {} because of pending remove", region.toString(false));
	return;
	}
	auto read_buf = buffer.tryGetReadBuffer();
	RUNTIME_CHECK_MSG(read_buf != nullptr, "failed to gen buffer for {}", region.toString(true));
	DB::WriteBatchWrapper wb{run_mode, getWriteBatchPrefix()};
	wb.putPage(region_id, applied_index, read_buf, region_size);
	page_writer->write(std::move(wb), global_context.getWriteLimiter());
	region.updateLastCompactLogApplied(region_task_lock);
	}

RegionPersister::doPersist acquires a lock and calls PageStorage::write with the lock. This means when we're persisting Region meta, all other threads can not do the persistence for other Region meta. Which is not reasonable.

What is changed and how it works?

There is a region_task_lock to ensure that only one thread could call RegionPersister::doPersist at the same time. And PageStorage support multi-thread reading and writing for different page_id. There is no need to acquire another lock in RegionPersister::doPersist that could slowdown the raft apply process

And also remove calling KVStore::persistRegion with a null region_task_lock. So we can simplify codes and remove the member RegionPersister:: RegionManager

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

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Reduce the impact of disk performance jitter on write throughput

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

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

Needs approval from an approver in each of these files:

• OWNERS

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]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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 kubernetes/test-infra repository.