• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

HAProxy devel Multithreading

Scheduled Pinned Locked Moved Cache/Proxy
2 Posts 2 Posters 589 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    michaelschefczyk
    last edited by Mar 8, 2019, 4:36 PM

    Dear All,

    The HAProxy devel package includes the option to set threads in order to provide more CPU capacity to HAProxy. That option does come with a substantial warning message.

    Would anyone be so kind to share experience in this field? Relevant aspects should include ACL and SSL offloading. Does HAProxy really not work upon setting a few threads (e. g., 4 on more powerful 8-12 core CPUs)? Are there other real downsides, such as crashes of HAProxy or the OS or the like?

    Regards,

    Michael Schefczyk

    P 1 Reply Last reply Mar 8, 2019, 6:25 PM Reply Quote 0
    • P
      PiBa @michaelschefczyk
      last edited by Mar 8, 2019, 6:25 PM

      @michaelschefczyk
      Recently (26-1-2019) haproxy itself removed the warning from their docs, the package on pfSense should get a little update to remove that warning as well..

      "It was mentioned when releasing 1.8 but early bugs have long been
      addressed"
      http://git.haproxy.org/?p=haproxy.git;a=commit;h=1f672a8162eda18c404c6784dd749b6e061e2e4d

      Afaik there are no issues anymore.. (Which in the early days used to included haproxy crashes and hangs spinning at 100% cpu usage of a core..)

      1 Reply Last reply Reply Quote 1
      1 out of 2
      • First post
        1/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received