> On Feb 10, 2016, at 6:56 , Will Halsall <[email protected]> wrote:
>
>
> After upgrading to packetfence 5.6.1 the results of /usr/local/pf/bin/pftest
> mysql tuner indicate we have not got enough innodb_buffer_pool_size. In line
> with the documentation, previous versions where happy with 1G but now it
> thinks I need over 2G. Is this to be expected?
>
Nothing in the database itself has changed that would make that a requirement.
The results from mysqltuner may simply reflect the fact that your database has
grown in the meantime.
>
> Everything else is working fine
If it ain’t broke…
Tuning the buffer_pool_size is a complicated matter.
It’s a cache, so the larger the better in general, but any memory you use for
it will not be available to other processes.
Past a certain point it makes no different how large you make it.
mysqltuner is a tool. Not a bad one but I would not rely blindly on it,
especially if it contradicts actual experience you have with the system.
If you notice slow queries or high cpu usage caused by the database, then
optimise the database.
Otherwise, thread carefully.
Best regards,
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
