On Thu, 18 Oct 2007 19:31:16 -0400, Steve Bireley <[EMAIL PROTECTED]> wrote:
>Hi Alan, >For telnet, the SSL session resume is insignificant since the sessions last so long. Further, interactive sessions typically result in very little traffic because users type slowly and the 3270 datastream is prett y efficient. We have a SSL proxy product that handles 1000's of users and uses very little CPU (Windows OS). We do get spikes in CPU usage when something happens on the network that disconnects 100's of users, who the n reconnect simultaneously. That is rare though. > >Steve Bireley >BlueZone Software >www.bluezonesoftware.com I think you are probably right. According to the z/VM performance report, a new session connect takes about 3x as many CPU cycles as a reconnect. That was why I was concerned. On the other hand, it is beginning to look like these numbers are trivial . The highest cost given, for new session connects and 1024-bit keys, is 84 ms total CPU on a 2064-109. My peak rate (on one of our 5 VM systems) appears to be 50 connects per HOUR: 50 * 84.0 / (60*60) / 1000 = 0.00117 = 0.117% of one engine of a 2064 -109 0.00117 * 174 MIPS = 0.20 MIPS (Does that look right?) Assuming Model MIPS MIPS/processor 2064-109 1563 174 MIPS Source: Technology News <http://www.tech-news.com/publib/pl2064.html> I haven't included the costs of the actual data transfer, because I don't know how to get the number of bytes, but it may also be trivial.
