Changes between Version 12 and Version 13 of RamUsage


Ignore:
Timestamp:
06/24/13 21:30:44 (3 years ago)
Author:
chris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • RamUsage

    v12 v13  
    1414Key figures to consider in the above graph is the value for the amount of current committed and active RAM, in this case 8.82GB and 4.63GB and also the amount of maximum committed and active RAM, in this case 4.30GB and 5.12GB. 
    1515 
    16 The RAM increase has made a significant amount of RAM available for caching and buffers and this has the knock on effect of speeding up the time to serve frequently accessed files to clients as they are held in RAM rather than being read from disk -- the [https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/http_loadtime.html average loadtime for pages] is now less than half it was before the additional RAM was added (12.15 milli seconds compared to 31.59 milli seconds). 
     16The RAM increase has made a significant amount of RAM available for caching and buffers and this has the knock on effect of speeding up the time to serve frequently accessed files to clients as they are held in RAM rather than being read from disk -- the [https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/http_loadtime.html average loadtime for pages] is now less than half it was before the additional RAM was added (12.15 milliseconds compared to 31.59 milliseconds). 
    1717 
    1818The sawtooth pattern is caused by MySQL slowly increasing it's memory usage as more things are cached, the dramatic dips are caused when MySQL is restarted, this is made clear in the graph below which tracks the memory used by some of the key processes on the server: 
    … …  
    2828[[Image(puffin-swap-month-2013-06-24.png)]] 
    2929 
     30Since the RAM was increased from 4GB to 8GB the server hasn't use any swap space. 
    3031 
     32