> Got it, thanks! In this case this sounds very useful. Do we understand the > performance impact?
I don't think we fully understand it. It's a question of additional research and benchmarking. So preliminary conclusions, based on common sense and my experiense of usage Ignite in production, are following: 1. CPU is not a bottleneck in most of Ignite use-cases. Especially when we use it as a in-memory database. 2. TDE mostly will increase CPU usage: SSL + pages encryption/decryption. В Пт, 02/03/2018 в 08:33 +0300, Dmitriy Setrakyan пишет: > On Fri, Mar 2, 2018 at 8:29 AM, Nikolay Izhikov <nizhi...@apache.org> wrote: > > > Hello, Dmitriy. > > > > Thank you for feedback! > > > > > Will it be supported? > > > > Yes. > > > > TDE shouldn't broke any of existing Ignite features. > > It adds some encrypt/decrypt level when we writing and reading pages > > in/from PDS. > > > > Got it, thanks! In this case this sounds very useful. Do we understand the > performance impact?
signature.asc
Description: This is a digitally signed message part
