Bug 1273544 - enable KeepAlive for bugzilla.redhat.com?
Summary: enable KeepAlive for bugzilla.redhat.com?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: 4.4
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-20 16:21 UTC by Cole Robinson
Modified: 2018-12-09 06:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-17 07:02:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Cole Robinson 2015-10-20 16:21:10 UTC
HTTP KeepAlive doesn't seem to be enabled for bugzilla.redhat.com. Maybe there's explicit reasons, but if not, it could be a decent time and bandwidth saver for XMLRPC users via python-bugzilla.

I see the bugzilla docs mention that it should be disabled: https://www.bugzilla.org/docs/4.4/en/html/configuration.html

But FWIW it appears bugzilla.mozilla.org _does_ have KeepAlive enabled:

$ curl -Iv https://bugzilla.mozilla.org 2>&1 | grep -i 'connection #0'
* Connection #0 to host bugzilla.mozilla.org left intact

Comment 1 Jeff Fearn 🐞 2015-11-23 06:37:16 UTC
Muhammad, I think we should get some performance testing on KeepALive on and off as part of the BZ 5.0 upgrade.

While it does mean the server needs to serve more connections simultaneously it also means that the ajax requests should be handled faster for web users, so it's worth comparing them during a stress test.

Comment 2 Cole Robinson 2016-01-22 13:36:53 UTC
Note if/when this is enabled on partner-bugzilla.redhat.com I can give it a spin

Comment 3 Jeff Fearn 🐞 2016-02-25 04:58:29 UTC
Taking this out of sprints until we have agreed with Ops on how we want to run this.

Comment 4 Jeff Fearn 🐞 2016-06-17 07:02:23 UTC
Moved to RT


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