The Reliable, High Performance TCP/HTTP Load Balancer
HAProxy implements an event-driven, mono-process model which enables support
for very high number of simultaneous connections at very high speeds.
Multi-process or multi-threaded models can rarely cope with thousands of
connections because of memory limits, system scheduler limits, and lock
contention everywhere. Event-driven models do not have these problems because
implementing all the tasks in user-space allows a finer resource and time
management. The down side is that those programs generally don't scale well on
multi-processor systems. That's the reason why they must be optimized to get
the most work done from every CPU cycle.
Authors:
--------
w@1wt.eu
- Developed at server:http
- Sources inherited from project openSUSE:Factory
-
5
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/haproxy && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_service | 0000000752 752 Bytes | |
_servicedata | 0000000224 224 Bytes | |
haproxy-1.6.0-makefile_lib.patch | 0000000764 764 Bytes | |
haproxy-1.6.0-sec-options.patch | 0000001359 1.33 KB | |
haproxy-1.6.0_config_haproxy_user.patch | 0000003040 2.97 KB | |
haproxy-2.7.8+git0.58c657f26.tar.gz | 0004302154 4.1 MB | |
haproxy-rpmlintrc | 0000000172 172 Bytes | |
haproxy-user.conf | 0000000077 77 Bytes | |
haproxy.cfg | 0000000769 769 Bytes | |
haproxy.changes | 0000375345 367 KB | |
haproxy.init | 0000010172 9.93 KB | |
haproxy.spec | 0000008174 7.98 KB | |
local.usr.sbin.haproxy.apparmor | 0000000070 70 Bytes | |
series | 0000000117 117 Bytes | |
usr.sbin.haproxy.apparmor | 0000001009 1009 Bytes |
Revision 130 (latest revision is 150)
Dominique Leuenberger (dimstar_suse)
accepted
request 1084061
from
Marcus Rueckert (darix)
(revision 130)
- Update to version 2.7.8+git0.58c657f26: * [RELEASE] Released version 2.7.8 * MINOR: listener: remove the now useless LI_F_QUIC_LISTENER flag - Add handling for the new startup logs in /dev/shm in the apparmor profile
Comments 0