meeeejin / mysql-nvdimm-caching Goto Github PK

What if the user defines NVDIMM caching tables instead of a fixed NVDIMM cached page definition?
To be concrete, the user defines NVDIMM caching pages in a table granularity in my.cnf

innodb_dynamic_nvdimm_tables="tpcc2000/new_orders;tpcc2000/order_line"

Server automatically store the tablespace ids of nvdimm caching pages at server starts ( atsrv_start()).

Advantages: This feature makes NVDIMM caching more intuitive. Moreover, we can adopt any size of the TPC-C database. (we can save 850 Pro 😃 )

Disadvantages: We can't track non-table granularity NVDIMM caching pages (i.e. STOCK table). This would be the future work.

if you feel this feature makes sense, then how about leaving this feature as an independent branch?
You can check an implementation here, features/dynamic-caching

Related documentation 🇰🇷