@TugBoat wrote:
Firstly, I should say that this is not a complaint - it is more that I would like to understand something that appears unusual to me.
I am running FreePBX (13.0.124 from distro) in a virtualised ESXi 6.0 environment on a system using SSD. (Yes, I am aware of all the caveats etc about virtualised/SSD etc.) As part of most installations in this environment I do the normal modifications to reduce the write rate based on the underlying SSD storage. This includes:
- moving /tmp to RAM
- moving /var/log to RAM (with save/restore on shutdown/start etc.)
- update the mount options to include: noatime,data=writeback,commit=60
- run without swapOn the whole this normally works well and prior to running FreePBX in this environment the daily write rate was about 0.07GB for two VMs (a FreeBSD router, and a Linux server).
When I install FreePBX in this environment my daily write rate goes up be a factor of 10 to 0.70 GB. Now this is probably acceptable, however, I am wondering exactly what all this write traffic is?
Even on a physical disk based system the disks would be active almost 100% of the time. The ESXi performance information shows continues write rates of 15 KByte/Sec (avg) for the FreePBX VM.
My installation has 2 x VOIP Phone, 1 x ATA (FXO+FXS) Trunk, 1 x IAX2 Trunk, 1 x SIP Trunk to external provider (60sec registration rate).
Another interesting thing is that if I run a copy my FreePBX system connected to an 'empty' network (ie. disconnected from the world) then the write rate drops a little, but not that much.
So what I am trying to understand is where exactly this write traffic is occurring and what it is related to?
I should add that altering the commit rate on the ext4 file systems doesn't appear to have much effect on the write traffic.
Thanks,
Tim
Posts: 4
Participants: 3