I'm using a secure server with a webapp to answer queries from a LWP client using https. I need https, since I want the transfer encrypted, but I'm finding it is slow.
Whereas a query to the server unencrypted gives a response of 0.07 seconds, over SSL it takes 0.38 seconds! Since this gets hit regularly, the delays add up, and so overall response is noticeably slow. Is this the price you pay for secure transmissions, or is there some configuration parameter I can tweak to reduce this delay? I'm using libwww 5.64 with Crypt::SSLeay 0.23 and openssl 0.9.6c. All are Debian packages (and so security bugfixes are back-ported). I tried using IO::Socket::SSL, but it wouldn't connect to my secure server. (Again - I just installed the Debian package, since README.SSL says IO::Socket::SSL OR Crypt::SSLeay are supposed to be "plug-and-play"). Any ideas on how I can improve performance? I suspect if I wrote a custom SSL Server/Client with persistent connections I'd get a large performance boost, but I really don't have the time to go that far (although if there's a ready-made framework I suppose I could adapt easily. It'd still take some time though.) -- .. Trevor Phillips - http://jurai.murdoch.edu.au/ . : Web Technical Administrator - [EMAIL PROTECTED] : | IT Services - Murdoch University | >--------------------------------------------------------------------< | On nights such as this, evil deeds are done. And good deeds, of / | course. But mostly evil, on the whole. / \ -- (Terry Pratchett, Wyrd Sisters) /
