Hello,
I'm working on a plan to roll out MariaDB per table data at rest
encryption. Reading through the docs
(https://mariadb.com/kb/en/data-at-rest-encryption-overview/), I
understand that "Using encryption has an overhead of roughly 3-5%." I'd
like to know what this 3-4% refers to. I am assuming this is a penalty
related to transactions a second (as the referenced blog post discusses:
https://mariadb.com/resources/blog/table-and-tablespace-encryption-on-mariadb-10-1/).
I am hoping I can access the MariaDB community brain trust to understand
the overhead of deploying encryption as related to:
* Disk: what overhead can I plan around for disk space?
* Scale considerations: in my environment I am looking at encrypting
around 100,000 smaller tables (spread out over numerous databases).
With the tables being encrypted, will they be decrypted and encrypted on
demand (as opposed to being "decrypted" on startup)?
* Index query performance: does encryption have an effect on how
indexes are utilized that I would need to plan against?
Are there other factors that others consider when deploying data at rest
encryption?
Best,
Mike
_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp