Browse the documentation

Early preview

Supervisor variants

To keep the common case small, oee-stub is compiled ahead of time in two variants for every target, and oee build selects the smallest one that satisfies your manifest. You never choose a variant by hand.

The two variants

VariantSupervisor overhead (design target)Contains
coreUnder 3.0 MBIntegrity verification, sandboxing, native CPU and memory capping, and every exit event except message brokers and the inbound webhook: duration, cron, timestamp, idle, utilization, signal, checkpoint, log_match, on_task_complete, file_watch, tcp_probe, process_watch, command and the HTTP and HTTPS poller http_poll.
extendedUnder 6.0 MBEverything in core, plus the message-broker sources (kafka, mqtt, nats, redis), the inbound webhook listener, the auto-scaler and the built-in load balancer.

How the variant is chosen

  • A manifest that uses none of the extended capabilities always receives the core variant.
  • A manifest with a kafka, mqtt, nats, redis or webhook exit event, or with autoscale.enabled: true, receives the extended variant.

oee inspect prints the embedded policy summary of a built binary, from which you can see the capabilities its manifest uses.

Footprint at run time

The design target for the core variant with no load-balancer connections is less than 6 MB of RSS and less than 0.1% CPU at a one-minute HTTP exit-event polling interval. Proxied connections are budgeted separately: less than 20 KB of supervisor memory per idle connection in tcp mode. Performance specifications lists every target.