Reducing Yocto and OpenWRT RAM Usage by Switching from OpenSSL to wolfSSL

On Yocto Linux Scarthgap, the wolfSSL endpoint process peaks at 10–13 KB of heap + stack, compared with 750–790 KB for OpenSSL, for an ECDHE P-256 / ECDSA P-256 / AES-128-GCM connection. These figures apply in both directions and to both TLS 1.2 and TLS 1.3.

On OpenWRT using uclient-fetch to grab 100k of data, libustream-wolfssl peaks at 45 KB while libustream-openssl peaks at 570 KB.

The point is resource consumption and cost reduction in your BoM (Bill of Materials). Sourcers in the consumer electronics industry know that AI is having an immense impact on commodity memory pricing. As a point of reference, DDR4 4Gb (256Mx16) was $2.70 about a year ago when ordered in large volume. Today it is roughly $15.

On November 10th, we will be having a webinar about switching from OpenSSL to wolfSSL in order to reduce memory usage. Our very own Anthony Hu will be presenting on how to do it in a Yocto and OpenWRT build. He will show you how to bring cost savings to your Embedded Linux based products. Stay for the Q&A session where you can ask questions about other low resource environments such as Bare Metal. Send a message to facts@wolfssl.com to make sure you get added to our mailing list to get notifications of the registration link for this and other upcoming webinars and events.

If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.

Download wolfSSL Now