[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Fri, 5 Feb 2010, Rob Beard wrote:
I suspect in this instance, it doesn't know that the "disk" is RAM, so it's effectively copied the ramdisk (ext2) into a filesystem cache - although I imagine it's probably quicker to fetch the data from the cache than the (ram)disk though as it probably has less code to execute. (getting from a very simplified cache filesystem vs. traversing an ext2 filesystem)Yep, I presume not much difference in speed, but I guess every little helps. I suppose it's also simplier this way too not having to change things to disable the buffers.
AIUI, Linux will use all the free RAM as filesystem buffer space - and why not. This is why some programs will get pushed out to swap (when you have swap!) and a system may see an apparent speed-up - I think the kernel will prioritise the filesystem cache over programs that have not executed for a long time, but I suspect there are many checks on things like time last accessed and so-on. It's not an area I've really paid much attention to in recnet years.
Some of the files in the cache will be regularly executed executables - cron jobs, etc. and some will be the aterisk config files, and php source code files, images, etc. the web server reads, and so on. Also the music on hold files and other audio files it has read out of the flash drive...Ahh, so the actual space occupied by Asterisk etc isn't much then I guess?
Nope. Asterisk is just another program and not a very big one that that - although they keep on trying to bloat it all the time )-:
The sound files take up as much (or as little) space as you want. I store most codecs apart from the raw WAV files. In my Mk1 units, I even had the sound files in RAM - a Mk1 box looks like:
Filesystem Size Used Avail Use% Mounted on /dev/ram0 124M 110M 15M 88% / So the root filing system is 110MB which includes dsx$ du -sm /var/lib/asterisk/sounds/ 8 /var/lib/asterisk/sounds/ I've "leaned down" the Mk2's by removing some other stuff too. In-use: (output from top) PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1117 root -11 0 22864 11m 5048 S 0.0 4.7 77:13.99 asterisk that's a VoIP only box - a bo with analogue ports seems to be more: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 30956 root -11 0 33308 21m 4996 S 0.0 8.5 484:44.27 asteriskand one of my main peering boxes, VoIP only, handling 1000's of call an hour:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1654 root -11 0 40712 22m 4304 S 63 2.2 1161:32 asterisk It's generally very well behaved (when you get a stable version!) Gordon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html