On Wed, 13 Oct 2010 02:12:21 -0700 (PDT)
Ashish <amvya...@gmail.com> wrote:
> >
> > > Is the client machine at 100% CPU when you do that?
> >
> > With HTTP, I see client CPU at appx. 97%. However with HTTPS, it stays
> > at 53-55%.
And is the server at 100% CPU then?
If the client is not at 100% CPU, it shouldn't be the bottleneck,
unless you have something wrong in the client implementation.
> > sock = socket.create_connection((self.host, self.port),
> > self.timeout)
> > sock2 = ssl.wrap_socket(sock, self.key_file,
> > self.cert_file)
> > self.sock = CBSocket(sock2)
What is CBSocket? What happens if you just write:
self.sock = sock2
> > > Also, there's a feature request to reduce overhead of SSL
> > > connections, but it needs implementing:http://bugs.python.org/issue8106
> >
> > Well good to know this. Do we have any date when this will be
> > available? I feel like contributing to this but kind of over occupied
> > with several activities right now.
Probably not in Python 3.2 anyway. But given your client isn't at 100%
CPU when you launch your HTTPS test, it might not make a lot of
difference.
Regards
Antoine.
--
http://mail.python.org/mailman/listinfo/python-list
