Dynamic Data Masking consumes CPU resources to process connections, rewrite requests, and store logs. The CPU consumption is linearly proportional to the SQL *Net traffic that the Dynamic Data Masking service routes. You can use the SQL *Net and DBlinks traffic values to estimate the amount of CPU that the Dynamic Data Masking service consumes.
The Dynamic Data Masking resource consumption is approximately 1% of the server CPU and has no I/O overhead. The Dynamic Data Masking service requires approximately 1 GB for memory and some disk space for logs.
To calculate the CPU consumption, you must determine the round-trip value, which is the total packet traffic that a client and server sends and receives each second. The total round-trip value includes SQL *Net traffic and DBlinks.
Use the following variables and equations to calculate the CPU consumption: