What is a consequence of enabling encryption at rest?

Enabling encryption at rest involves securing stored data in its inactive state, ensuring that the data remains confidential and protected from unauthorized access. While this is vital for compliance and security in a data environment, it does have performance implications, particularly in terms of data processing and retrieval.

Specifically, when encryption is applied, there is an overhead associated with both the encryption and decryption processes. Every time data is accessed or loaded into a visualization, it must be decrypted before it can be used. This additional processing step generally results in an increase in both Viz Load Time and the load on the worker nodes handling requests for that data. Consequently, users experience longer wait times when loading visualizations, as the system must handle the extra computation involved in the encryption and decryption of data during these operations.

This increased burden can also affect the overall performance of the system, as more resources may need to be allocated to manage the rising workload associated with these operations, impacting performance metrics across the board. Thus, the implication of enabling encryption at rest is directly associated with an increase in Viz Load Time and Worker Load.