Hi Sam, In case its useful for comparison I looked at Swift SSL performance in general a while back: https://region-a.geo-1.objects.hpcloudsvc.com/v1.0/AUTH_19cbcca3-a4b8-4b90-9332-c9bffd02285f/public_referenced/swift_perf6.pdf I didn't see pound hurting performance as much as you did, but our configs may have been different. -Stuart PS There's currently some work being done to allow the Glance client to disable SSL compression on a per connection basis: https://blueprints.launchpad.net/python-glanceclient/+spec/ssl-connect-rework If this gets merged it will cover the glanceclient -> glance data path but not the glance -> swift part. (With a bit of luck that may get added later.) On Mon, 8 Oct 2012, Sam Morrison wrote: > OK we changed to use nginx as opposed to pound and got a huge increase in speed. > > With taking glance out of it and talking directly to swift an image took 1m38s to download with pound in front. > With nginx this took just 5s not sure what is wrong with pound, we haven't changed any settings for pound or nginx. > > Sam > > > On 08/10/2012, at 2:50 PM, Sam Morrison <sorrison at gmail.com> wrote: > >> Hi, >> >> We've recently enabled ssl on our swift-proxy and now glance is incredibly slow. I've read some stuff about disabling zlib compression etc. >> >> Has anyone got a good fix for this? >> >> We're using Ubuntu 12.04 >> >> Cheers, >> Sam >> >> > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >