maria-developers team mailing list archive

[Roberto Spadim <roberto@xxxxxxxxxxxxx>]

Hi guys, i was thinking about ideas for query cache...

there's an mdev about partitioning query cache (
https://mariadb.atlassian.net/browse/MDEV-4454)

instead of this, why not use a HEAP storage engine (with partitioning), or
maybe a myisam or aria or innodb as "backend", and write a "frontend"
(query cache) that execute commands over this storage engine?

i'm talking about, changing the query/table/result blocks of query cache,
to query/table/result tables

when start mysqld truncate these tables
when add new query "insert" to these tables
when a table prune occur, "delete" from these tables
when flush, optimize these tables
when reset query cache, truncate this tables

these tables could be at mysql schema, if they don't exists create as
ENGINE=MEMORY for example

since we must have a MAX SIZE for query cache, we could add a MAX SIZE for
HEAP engine and a LOW MEMORY algorithm (
https://mariadb.atlassian.net/browse/MDEV-4675)

at high level, what you think about this idea?

-- 
Roberto Spadim