<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — Scaling with SSL]]></title>
		<link>https://www.wolfssl.com/forums/topic198-scaling-with-ssl.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic198.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Scaling with SSL.]]></description>
		<lastBuildDate>Tue, 13 Mar 2012 19:14:10 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Scaling with SSL]]></title>
			<link>https://www.wolfssl.com/forums/post456.html#p456</link>
			<description><![CDATA[<p>Hi,</p><p>Why is CyaSSL a great solution when you have millions of connections per server?&nbsp; Memory consumption per connection can be as low as 3k, varying with the size of input and output buffers.&nbsp; This brings CyaSSL’s runtime memory consumption to <strong>3-36kB</strong> depending on buffer size.&nbsp; Input and output buffers are created on demand when smaller than MAX_RECORD_SZ unless the user turns on STATIC_CHUNKS_ONLY.&nbsp; </p><p>In contrast,&nbsp; OpenSSL typically consumes 50-140k per connection.&nbsp; CyaSSL emphasizes small size, speed, and low memory use.&nbsp; These attributes make CyaSSL ideal for scaling on a huge magnitude.&nbsp; &nbsp;Other libraries often run into problems when trying to scale to hundreds of thousands of connections for applications like load balancing or cloud services.&nbsp; We have users doing just that.&nbsp; </p><p>Want to hear about how CyaSSL is being scaled in the cloud?&nbsp; Contact us and we&#039;ll share some of the use cases currently in production.</p>]]></description>
			<author><![CDATA[null@example.com (chrisc)]]></author>
			<pubDate>Tue, 13 Mar 2012 19:14:10 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post456.html#p456</guid>
		</item>
	</channel>
</rss>
