Switching to CRI-O as container runtime we can see up to
30% performance improvement for Collectord. The reason for
that is the format of the Logs. Parsing JSON logs is expensive on a high amount of logs, as strings in JSON fields can
have escaped symbols, requiring Collectord to allocate more memory for processing data, and more time on discovering
OpenShift is planning to switch to CRI-O in 2019, and we want to be ready for that. Collectord supports logs in CRI-O format starting from Version 5.0 (released in September 2018).
Test on CRI-O. Forwarding 5,000 1Kb events per second. Default configuration.
Comparing to the Version 5.3 running with Docker as container runtime
CPU usage went down from
19%. Memory usage is in the same range of
You can test Developer Preview of OpenShift 4 right now. OpenShift 4 has a straightforward way to get it up and to run on AWS, KVM or OpenStack. It takes less than 20 minutes to get it up and running on AWS.
Our installation instructions as always work out of the box for OpenShift 4. Collectord discovers and forwards logs (from CRI-O runtime) and collects metrics. Small adjustments require for some Control Plane components, to get all the Control Plane metrics.
Focus on your applications, and let us take care of infrastructure monitoring and log forwarding. We got your covered.