Bug 1330038 - Http KeepAlive is disabled in 6.2 cause performance issues
Summary: Http KeepAlive is disabled in 6.2 cause performance issues
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Performance
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-04-25 10:29 UTC by Pradeep Kumar Surisetty
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-25 17:30:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1160480 0 unspecified CLOSED Http KeepAlive is disabled causing performance issues 2023-09-14 02:50:14 UTC

Internal Links: 1160480

Description Pradeep Kumar Surisetty 2016-04-25 10:29:47 UTC
Description of problem:

Http KeepAlive is disabled in 6.2 cause performance issues

It was enabled by default in 6.1 



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

keepALive is disabled 

Expected results:

keepALive need to be enabled

Additional info:

Comment 1 Craig Donnelly 2016-04-25 10:38:21 UTC
Original BZ that was corrected for 6.1 Release: https://bugzilla.redhat.com/show_bug.cgi?id=1160480

Comment 3 Mike McCune 2016-05-25 17:30:39 UTC
we do have KeepAlive configured on, it is in:


/etc/httpd/conf.d/05-foreman-ssl.d/katello.conf:KeepAlive On
/etc/httpd/conf.d/05-foreman-ssl.d/katello.conf:MaxKeepAliveRequests 10000

Comment 4 Pradeep Kumar Surisetty 2016-05-25 17:33:21 UTC
We shoud include "KeepAliveTimeout 5" too
This has given some improvements with 6.1. 

Will try to get performance differences with/without KeepAliveTimeout on 6.2


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