Hi mike, It seem that openssl since version 0.9.8b zlib compression is enable by default. This is the problem of cpu usage of stunnel. Is it possible to force it disable it by 'compression = none' in a next version of stunnel ? reference: http://www.mail-archive.com/[email protected]/msg49919.html Thank's. Ludovic. Le 07/12/2011 23:51, Ludovic LEVET a écrit :
Hi Mike,
Thank's for your quick job !
So, i have a good new and bad new.
First : Good new It is working !
Second : Bad new Even if i remove on my conf file 'compression = zlib' (on server and client) the compression is enable. I have see that, by the cpu used by my server for the process stunnel. With version 4.50 (on the client) with a file (500MB) to transfert (at 3.5MB to my home), the cpu of server is at 15% for the process stunnel . With version 4.51b (on the client) with the same file at same speed take 85% of cpu for the process stunnel.
Now, to disable compression on my client with 4.51b , i rename the zlib1.dll to zlib1.dll.bak and restart stunnel, after the same transfert take 15% - 18% of cpu on my server for the process stunnel .
I think that openssl enable by default compression if remote openssl server suport it by default.
my config :
client : windows 7 64bits with stunnel 4.50 or 4.51b server : fedora i386 with openssl-1.0.0b and stunnel 4.50 (compiled from me)
Thank's.
Ludovic.
Le 07/12/2011 16:22, Michal Trojnara a écrit :
I wrote:
I'm convinced. I'll try to find a few hours next week to build Zlib and to update OpenSSL.
Please try: ftp://ftp.stunnel.org/stunnel/beta/stunnel-4.51b1-installer.exe
Mike _______________________________________________ stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
_______________________________________________ stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
-- ------------------------------------------------------------------------------------------------------------------------- Ce message inclut une signature numérique. Il certifie que l'expéditeur et le contenue du message sont authentiques. Si votre logiciel de messagerie est compatible, Il doit garantir que le document n'a pas été altéré entre l'instant où l'auteur l'a signé et le moment où le lecteur le consulte. Loi n°2000-230 du 13 mars 2000 Art. 1316, 1316-1, 1316-2, 1316-3, 1316-4 du Code civil. -------------------------------------------------------------------------------------------------------------------------