hi
i’m using mikrotik router os for my NAS. i have 15 NAS. There is dhcp,ntp,ppp,routing,security,system packages on it. I’m notice that on all NAS uses only 10% of memory on board. For example if is 512Mbyte memory on server the router OS used only 50-60Mbyte, and if it 2Gbyte of memory on board only 200-220Mbyte is in use.
And one more. Router’s with 2Gbyte memory uptime is >1000 hours and other routers with 1Gbyte memory or less uptime <100 hours.
but why only 10% from memory???
when router use 50MB of 512MB and I add to it 512MB (summary 1GB) it start to use 100MB. why it cant use 100MB from 512MB installed memory?
Not for our routers, all of them show different percentages:
Try to do something that will definitely eat up memory, like enable webproxy with “cache on disk” unckecked (cache in memory)
Is it possible that this is normal and, like Normis said, you aren’t doing anything memory-intensive? Perhaps either the Linux kernel VM or some other component of the system somewhere preallocates 10% of physical memory at minimum by default, so that you will never see anything MORE than 90% of memory free at any given time?
There are more often reboots occur in routers with less memory (512MB or 1GB for example) and there are no reboots on the router with 2Gb memory. In this case I must to bought 2GB memory on all routers just because OS can’t use more than 10% from all installed memory bank. Do you think it’s OK?
It’s not true, I posted a screenshot to prove it, I can post more. This is just in your router. We have plenty of X86 devices and we don’t have this problem. If a router rebooted, the reason will be written in the log. Read it and see the cause. Or send the supout.rif to support and we will see reason reboot
I’ve do so already, send supout.rif, but the answer was “it’s your hardware problem”. I have 4 different hardware configuration.
there is nothing in my log after reboot, just “mar/31/2009 12:24:42 system,error,critical router was rebooted without proper shutdown” but it’s not a power fault.
maybe I could turn on some debug to find out the reason?