ASKING. Memory-InnoDB Engine that easy peasy to you guys

There is the 'MEMORY' engine exist which is actually useless since table lock.
Impossible to use under mid-large size workload.
(Real heavy and critial load may choose the RockDB for practical reason.)

Me and internet people tried to self-compile the innodb as memory innodb
by skip or commenting the disk writing codes but not easy to.

So, I strongly asking you to put a memory innodb as a built int engine like rockdb(since Rockdb so slow even under zero compression option and small-mid size workload not like the big-tech compony where the origin).

This activity may help the small-mid size group choose mariadb for fastest requirement.
People needs the memory base table for some part but you guy not providing any solution.
Taht is why people keep shifting to redis or so which different platform.
Whay don't we providing just memory base innodb? We already have the solution(by skiping disk write part).
Current MEMORY table engine actually rubbish no where to use under professional environment. And no stable TokuDB available. RockDB so heavy/slow and hard to use.
Hope that don't mariadb and mysql neglecting only a cloud base memory innodb company sales.

Just people use perfect innodb on the memory without pain. Then we don't need redis or mongo or any other shitty db collaboration.

Only need is a make file for memory innodb(and some defines in the source code isolate disk wring part). Then we can shit and stay with the mariadb with high performance.
If you not so comfortable with memory size issue, just put a 'size limit' config as mandatory setting for the memory innodb. To you guys, it is easy peasy. Isn't it?

It is time to unlock the mariadb performance.

(The only reason I have quit the self-compiling is the source code not easy to read to me. but you guys. Even may do this within a minutes.)