Re: SSL and Performance

the additional ssl overhead is going to depend on the size of your pages,
and how mush cpu they take. ssl is handeled by iis. for example, to use ssl
on your images (which you will do to prevent the mixed mode error alert),
the cpu overhead will be high, say 10x, because there is so little cpu with
a simple file download. but an aspx page uses a more cpu, it may only be a
10%.

ssl uses also uses more network bandwith. you are correct, there is also
additional overhead in setting up the session, but again its cost will
depend on the page cost.

may sites offload the ssl to the firewall proxy anyway.

-- bruce (sqlwork.com)


"Ryan Ternier" <rternier@xxxxxxxxxxxxxxxx> wrote in message
news:%23US6POkNFHA.3076@xxxxxxxxxxxxxxxxxxxxxxx
> My Company is looking to implement SSL encryption on a few of our software
> projects.
>
> We deal mostly with local governments so information needs to be secure
> between the client and our servers.
>
>
> We've heard SSL can be costly on the initial handshake.. how costly?
>
> Our Server is currently:
>
> Server 2000,
> -running around 200 websites
> -ASP and ASP.NET on the same machine
>
> Total Server visits per day: 20,000 - 50,000
>
> Total visits to the applications needing SSL : 1000-2000 (Depending on how
> busy the city is).
>
>
>
> Rternier
> Code Monkey


.

Relevant Pages

  • Re: Dealing with SSL processing via hardware
    ... If the "hardware" is basically just a single CPU computer with Linux and OpenSSL installed on ROM wrapped in a sealed box, then I would suppose you could emulate the exact same performance characteristics by adding another CPU to your main server computer and only using that CPU for running the same SSL and socket software you would have inside the sealed box. ...
    (borland.public.delphi.non-technical)
  • Re: Dealing with SSL processing via hardware
    ... That probably depends on the hardware. ... If the "hardware" is basically just a single CPU computer with Linux and OpenSSL installed on ROM wrapped in a sealed box, then I would suppose you could emulate the exact same performance characteristics by adding another CPU to your main server computer and only using that CPU for running the same SSL and socket software you would have inside the sealed box. ...
    (borland.public.delphi.non-technical)
  • Re: where to put SQL Server ?
    ... Overhead won't be huge, as performance of SQL ... Server will be lokely limiting factor, ... And it is harder to implement than SSL encryption for TDS, ...
    (microsoft.public.windows.server.security)
  • Re: Implementing SSL on Exchange5.5 OWA
    ... SSL in terms of processor and seriously consider not putting the CA on the ... > I would like to implement SSL on a win2k server running ... > additional processor overhead and memory requirements is ... >>If you're against the wall already, ...
    (microsoft.public.exchange.admin)
  • Re: SSL Telnet
    ... You need to set up SSL on the server. ... encryption, the CPU has to do it. ... not a good idea if you are low on CPU and/or memory. ... involves math with very long integers. ...
    (comp.sys.ibm.as400.misc)