Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
Some of the logic in the buf_flush_page_cleaner thread is based on processing one tablespace at a time. I did not fully think through this, but I believe that the global buf_pool.page_hash could be split into hash tables that are attached into the individual tablespaces.
Most callers of buf_page_get_gen() should be able to access the tablespace object conveniently. For the bulk of the calls, it would be available via dict_index_t::space. For all tablespaces that are known to InnoDB, there will be a fil_space_t object allocated in memory, even for tables or files that have not been accessed during the lifetime of the server process.
Attachments
Issue Links
- relates to
-
MDEV-11378 AliSQL: [Perf] Issue#23 MERGE INNODB AIO REQUEST
-
- Open
-
-
MDEV-33966 sysbench performance regression with concurrent workloads
-
- Stalled
-