What should a SysOps administrator do to resolve this issue?
In the CPU launch options for the Lambda function, activate hyperthreading.
Turn off the AWS managed encryption.
Increase the amount of memory for the Lambda function.
Load the required code into a custom layer.
Explanations:
AWS Lambda does not have an option to activate hyperthreading, as it abstracts the underlying infrastructure. CPU performance in Lambda is determined by the memory allocation, which also allocates CPU power, but hyperthreading is not a configurable option for Lambda functions.
AWS managed encryption does not significantly affect the performance of CPU-intensive operations in Lambda functions. Turning off encryption would not resolve performance bottlenecks related to CPU usage.
Increasing the amount of memory allocated to a Lambda function also increases the CPU allocation, which can enhance performance for CPU-intensive tasks. Since Lambda functions allocate CPU power proportional to the memory, this option directly addresses the performance issue.
While using a custom layer can help manage dependencies and optimize the function’s code, it does not inherently increase the CPU resources or address the performance bottlenecks caused by CPU-intensive operations.
I rate that the answer is:
Increase the amount of memory for the Lambda function.