- config.yml: num.stream.threads can be set with KAFKA_STREAMS_NUM_THREADS (default unchanged: 1). Map processing was bottlenecked on a single stream thread while the host was mostly idle. - Unraid example: run 3 stream threads (topics have 3 partitions), and cap each JVM's heap via JAVA_OPTS. Without a cap each JVM defaults to 1/4 of the host's RAM, and the stack grew to ~14 GB. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| events-library | ||
| events-mod | ||
| events-processor-core | ||
| events-processors | ||
| events-server | ||
| events-server-syslog | ||
| events-server-web | ||
| infra-factorio-client | ||
| infra-factorio-server | ||
| infra-kafka-cluster | ||
| infra-kafka-pipe | ||
| kt-rcon | ||
| versions-platform | ||
| web-map | ||
| modules.md | ||