This repo contains a barebones Django project that uses Watchtower to record logs to AWS CloudWatch. A single view is defined to serve requests to / and respond with a simple Hello!. Internally, that view executes several logger.info calls to generate short messages for Watchtower to send to AWS.
Unfortuantely, there appears to be a performance regression when migrating from UBI8 to UBI9 and using code like this. In repeated experiments, UBI9 appears to be consistently ~10% slower than UBI8 running the same Python code.
The following instructions serve to demonstrate UBI9's performance regression compared with UBI8.
docker build -t ubi-minimal-perf-demo:ubi8 -f Dockerfile_ubi8 .
docker build -t ubi-minimal-perf-demo:ubi9 -f Dockerfile_ubi9 .You must have access keys for an AWS account, and those keys must have the ability to write to CloudWatch.
# enter your AWS access key id and secret access key.
# these are required for watchtower to send logs to AWS cloudwatch.
read -s CLOUDWATCH_AWS_ACCESS_KEY_ID
read -s CLOUDWATCH_AWS_SECRET_ACCESS_KEY
# optional env variables; code assumes these defaults if not set.
# CLOUDWATCH_AWS_REGION_NAME="us-east-1"
# CLOUDWATCH_LOG_GROUP="demo-log-group"
# CLOUDWATCH_LOG_STREAM_NAME="demo-log-stream"
# LOG_LEVEL="INFO"
# DJANGO_LOG_LEVEL="ERROR"# run the demo server on ubi8.
# add extra env variables with -e as needed.
CONTAINER_ID=$(docker run -d --rm \
-p 8000:8000 \
-e "CLOUDWATCH_AWS_ACCESS_KEY_ID=${CLOUDWATCH_AWS_ACCESS_KEY_ID}" \
-e "CLOUDWATCH_AWS_SECRET_ACCESS_KEY=${CLOUDWATCH_AWS_SECRET_ACCESS_KEY}" \
ubi-minimal-perf-demo:ubi8)
# verify ther container is running.
docker ps -f "id=${CONTAINER_ID}"
# run ab (apache bench) with a moderate number of requests.
# capture the output if you wish.
ab -c2 -n200 http://127.0.0.1:8000/ 2>&1 | tee /tmp/ubi8-demo-ab.txt
# save the container logs if you wish.
docker logs "${CONTAINER_ID}" > /tmp/ubi8-demo-logs.txt 2>&1
# kill the container
docker kill "${CONTAINER_ID}"Same as above instructions for UBI8, but s/ubi8/ubi9/g.
# run the demo server on ubi9.
# add extra env variables with -e as needed.
CONTAINER_ID=$(docker run -d --rm \
-p 8000:8000 \
-e "CLOUDWATCH_AWS_ACCESS_KEY_ID=${CLOUDWATCH_AWS_ACCESS_KEY_ID}" \
-e "CLOUDWATCH_AWS_SECRET_ACCESS_KEY=${CLOUDWATCH_AWS_SECRET_ACCESS_KEY}" \
ubi-minimal-perf-demo:ubi9)
# verify ther container is running.
docker ps -f "id=${CONTAINER_ID}"
# run ab (apache bench) with a moderate number of requests.
# capture the output if you wish.
ab -c2 -n200 http://127.0.0.1:8000/ 2>&1 | tee /tmp/ubi9-demo-ab.txt
# save the container logs if you wish.
docker logs "${CONTAINER_ID}" > /tmp/ubi9-demo-logs.txt 2>&1
# kill the container
docker kill "${CONTAINER_ID}"See the results directory of this repo for some typical examples I captured. It's difficult to eliminate or reduce all other variables, of course, but the tests captured here were all performed on gigabit ethernet (Google Fiber in NC, USA) to AWS us-east-1 with no other major local CPU or network activity.