Hi Michael, Out of curiosity, what do you mean by "Virtual DC" ? I'm not familiar with that term.
If you are using AstLinux 1.4.3 or later, the kernel /proc/[pid]/io stats are enabled. So, look for "read_bytes" and "write_bytes" in the output of the 'init' process: -- cat /proc/1/io -- For Asterisk, this should work: -- cat /proc/$(pgrep -f '^asterisk')/io -- See how quickly "read_bytes" and "write_bytes" increase over a set period of time. Next convert into IOP by guessing an average block size. Note: some of this Disk IO is to RAM based tmpfs, but would give you a worst case scenario. Additionally, 'htop' supports IO_RATE column (DISK R/W) that can monitor IO. Lonnie > On Jul 20, 2022, at 2:29 PM, Michael Knill > <michael.kn...@ipcsolutions.com.au> wrote: > > Hi Group > > I am virtualising most Astlinux installs and now moving to Virtual DC’s where > I have more control of the type of resources I allocate. One of these is the > type of storage and usually in the form of IOP’s. > For example I can purchase storage ranging from 100 IOP’s to 25,000 IOP’s. > Now although the difference in price is not huge, it does add up and I want > to try to minimise costs where possible. > I have been using 250 IOP’s and I have not seen any problems but just > wondering if this is too low? Even though am writing logs to KD, I assumed > that the Astlinux architecture was still pretty light on in regards to disk > writes. > > Thanks > Mike > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
