Changes between Initial Version and Version 1 of Ticket #670, comment 22


Ignore:
Timestamp:
06/02/14 13:34:01 (2 years ago)
Author:
chris
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #670, comment 22

    initial v1  
    139139The ones below 14 are not something to worry about -- the server has 14 CPUs, these are the concerning ones: 
    140140 
    141 * Sun, 25 May 2014 09:54:00 - 60.34  
    142 * Mon, 26 May 2014 06:25:56 - 20.50wiki/PuffinServerBoaLoadSpikes 
    143 * Mon, 26 May 2014 15:58:24 - 30.44 
    144 * Mon, 26 May 2014 18:45:39 - 25.06 
    145 * Tue, 27 May 2014 06:25:47 - 27.10 
    146 * Tue, 27 May 2014 08:47:04 - 43.91 
    147 * Wed, 28 May 2014 11:05:00 - 101.63 
    148 * Wed, 28 May 2014 13:52:26 - 92.50 
     141* Sun, 25 May 2014 09:54:00 - '''60.34''' 
     142* Mon, 26 May 2014 06:25:56 - '''20.50''' 
     143* Mon, 26 May 2014 15:58:24 - '''30.44''' 
     144* Mon, 26 May 2014 18:45:39 - '''25.06''' 
     145* Tue, 27 May 2014 06:25:47 - '''27.10''' 
     146* Tue, 27 May 2014 08:47:04 - '''43.91''' 
     147* Wed, 28 May 2014 11:05:00 - '''101.63''' 
     148* Wed, 28 May 2014 13:52:26 - '''92.50''' 
    149149 
    150150I suspect that if we renistate the memory allocation that was removed from MySQL by the "Roll back performance customisations and use stock BOA settings where possible" policy -- MySQL memory was reduced by 50%, see ticket:587#comment:11 and ticket:707#comment:39 -- then there is a chance that these spikes would be dramatically reduced. Ed / Jim -- are you willing to give this a try?