High CPU Usage

[prologic]

Heya 👋

I've been running goaccess for the past couple of days on Caddy log file(s) that look like this:

# ls -lah /var/log/caddy/access/*.log
-rw------- 1 caddy caddy 1.8M Jan  7 08:55 /var/log/caddy/access/...
-rw------- 1 caddy caddy 1.6M Jan  7 10:14 /var/log/caddy/access/...
-rw------- 1 caddy caddy 1.9M Jan  7 10:55 /var/log/caddy/access/...
-rw------- 1 caddy caddy  68M Jan  7 10:58 /var/log/caddy/access/...
-rw------- 1 caddy caddy 4.1K Jan  7 05:37 /var/log/caddy/access/...
-rw------- 1 caddy caddy 4.1M Jan  7 10:24 /var/log/caddy/access/...
-rw------- 1 caddy caddy 8.5M Jan  7 10:57 /var/log/caddy/access/...
-rw------- 1 caddy caddy 1.5M Jan  7 09:56 /var/log/caddy/access/...
-rw------- 1 caddy caddy 2.6M Jan  7 10:40 /var/log/caddy/access/...
-rw------- 1 caddy caddy 1.9M Jan  7 10:58 /var/log/caddy/access/...
-rw------- 1 caddy caddy  11M Jan  7 10:57 /var/log/caddy/access/...

And my local.d startup script looks like this:

# cat /etc/local.d/goaccess.start
#!/bin/sh

goaccess --daemonize --restore --persist \
	 --db-path /var/lib/goaccess \
	 --debug-file /var/log/goaccess.log \
	 --keep-last 28 --agent-list \
	 --with-output-resolver --jobs 1 \
	 --log-format caddy --real-time-html \
	 --geoip-database /etc/caddy/GeoLite2-City.mmdb \
	 -o /var/www/report.html \
	 /var/log/caddy/access/*.log

I'm seeing really high CPU utilization of the goaccess process. So much so that its saturaing my VM from it's primary work (reverse proxying). Have I misconfigured something here?