You might as well consider using a cluster of PacketFence servers.
The built in PacketFence clustering can already do that, using HAproxy.
> On Aug 11, 2016, at 4:29 AM, Torry, Andrew <[email protected]> wrote:
>
> Given we can throw more memory at the server and possibly even load-balance
> across multiple servers
> (using a Cisco ACE loadbalancer) it seems sensible to ramp these figures up.
Scaling is an art.
The first rule is to find what is the bottleneck.
Have a look at the built-in graphite metrics of PF.
They should allow you to see where time is spent.
Once you know that, then you can fix it and avoid spending your own time on a
wild-goose chase.
See also the apache mod-status page if in doubt (when a problem is happening).
It will tell you how many apache processes are currently running, and what they
are doing.
Best regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca/>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu/>) and
PacketFence (www.packetfence.org <http://www.packetfence.org/>)
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
