[DOC] Dump/Restore of the Buffer Pool makes little sense with flash
Bug #1097260 reported by
Aurimas Mikalauskas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.5 |
Triaged
|
Low
|
Unassigned | |||
5.6 |
Opinion
|
Undecided
|
Unassigned | |||
5.7 |
Opinion
|
Undecided
|
Unassigned |
Bug Description
[In:Percona Server Documentation]
Correct me if I'm wrong, but using buffer pool restore is not all that useful on flash storage since random/sequential makes little difference here. The only application with flash that I think still makes a good case is when you want the restore to be blocking i.e. restore buffer pool to the state it was, before you even allow any queries to hit MySQL.
To post a comment you must log in.
I don't understand the question. What's wrong with a non-blocking buffer pool restore on flash? Yes, LRU dump files are sorted for sequential reads on restore, which doesn't make much sense for flash storage, but it doesn't hurt either?