Bug 1004295 - pywbem initiates new HTTP connection with each request
Summary: pywbem initiates new HTTP connection with each request
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pywbem
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Safranek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-04 11:00 UTC by Jan Safranek
Modified: 2013-11-01 12:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-01 12:42:16 UTC
Target Upstream Version:


Attachments (Terms of Use)
Highly experimental patch (40.07 KB, patch)
2013-11-01 12:41 UTC, Jan Safranek
no flags Details | Diff

Description Jan Safranek 2013-09-04 11:00:10 UTC
Description of problem:
Each request inside WBEMConnection opens new TCP connection to CIMOM, which includes TLS handshake (if enabled). This slows down whole communication a lot.

Version-Release number of selected component (if applicable):
pywbem-0.7.0-16.20130827svn625.el7.noarch

How reproducible:
always

Steps to Reproduce:

import pywbem
c = pywbem.WBEMConnection("https://localhost", ("root", "opensesame"))
while True:
    c.EnumerateInstanceNames('LMI_Identity')

Actual results:
in wireshark, I see lot of separate TCP connections

Expected results:
One TCP connection with HTTP keep-alive enabled.

Comment 2 Jan Safranek 2013-11-01 12:41:11 UTC
Created attachment 818282 [details]
Highly experimental patch

Comment 3 Jan Safranek 2013-11-01 12:42:16 UTC
Using Connection: Keep-Alive did not have any significant performance improvements, I'm closing the bug for now.


Note You need to log in before you can comment on or make changes to this bug.