Answers.Body: <p>A lot depends on how much data you maintain in terms of contacts, participants, members, etc.  </p>
  
  <p>I have seldom seen any recent install of CiviCRM (on Drupal 7) running well on anything less than 1 gig, and I always recommend at least 1.5 gig; usually 2 gig.</p>
  
  <p>Sorry, but I suspect no amount of MySQL tuning is going to give you what you need with only 512M.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-24T22:36:18.153Z
Answers.LastActivityDate: 2015-08-24T22:36:18.153Z
Answers.UserDisplayName: DaveD
Answers.Body: <p>what was the version you were using before?</p>
  
  <p>the user interface is moving to be more reactive, and it means more smaller ajax requests than a big page loaded once in a while, it might have an impact.</p>
  
  <p>an issue i faced is the dashlets that tend to generate a lot of requests too, try to ask your users to remove them, see if things improve.</p>
  
  <p>as for the suggested size, i don't know, our servers are not vpn, so we got an order of magnitude more memory than your configuration.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-24T09:35:35.753Z
Answers.LastActivityDate: 2015-08-24T09:35:35.753Z
Answers.UserDisplayName: Xavier
Body: <p>I upgraded Civicrm to 4.6.6 (next 4.6.7) and had a lot of problems since then. My sql server has started consuming much more memory while everything was allright before the upgrade with 512M of RAM.
  After the upgrade, the server crashed because it was overconsuming memory. It never happened before. I lowered the values (of cache and tmp tables). I had then a issue with max connections reached. I restarted the server several times and try to find the good configuration but no success for now.
  What is a fair configuration of mysql server with drupal 7 and civicrm 4.6.7?
  Does anyone has an idea why the upgrade made this problem occur ?
  Thanks a lot
  Laure</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-25T02:16:06.200Z
Comments.Text: Do you mean that the server running MySQL has only 512M available, or that MySQL itself is configured to use only 512M?
Comments.UserDisplayName: Chris Burgess
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-02T16:37:23.597Z
Comments.Text: I am seeing a similar problem after upgrading to 4.6.8.   Memory usage warning and then mysql crashes.   No dashlets of any significance.
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-02T16:40:54.280Z
Comments.Text: Correction - cpu load warning before crash
Comments.UserDisplayName: Dave T
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-05T05:39:12.157Z
Comments.Text: DaveT, sounds like mysql is killed because of high memory use elsewhere (likely apache child processes).
Comments.UserDisplayName: michaelmcandrew
Tags: <mysql><configuration><performance>
Title: Upgrade to 4.6.6 : how to configure mysql server?
ThreadText: # Upgrade to 4.6.6 : how to configure mysql server?
  
  (Asked by: username_0 on 2015-08-24)
  
  I upgraded Civicrm to 4.6.6 (next 4.6.7) and had a lot of problems since then. My sql server has started consuming much more memory while everything was allright before the upgrade with 512M of RAM.
  After the upgrade, the server crashed because it was overconsuming memory. It never happened before. I lowered the values (of cache and tmp tables). I had then a issue with max connections reached. I restarted the server several times and try to find the good configuration but no success for now.
  What is a fair configuration of mysql server with drupal 7 and civicrm 4.6.7?
  Does anyone has an idea why the upgrade made this problem occur ?
  Thanks a lot
  Laure
  
  **Tags:** mysql, configuration, performance
  
  > **Comments:**
  > **username_1**: Do you mean that the server running MySQL has only 512M available, or that MySQL itself is configured to use only 512M?  
  > **username_2**: I am seeing a similar problem after upgrading to 4.6.8.   Memory usage warning and then mysql crashes.   No dashlets of any significance.  
  > **username_2**: Correction - cpu load warning before crash  
  > **username_3**: DaveT, sounds like mysql is killed because of high memory use elsewhere (likely apache child processes).  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_4 on 2015-08-24. Score: 1
  
  A lot depends on how much data you maintain in terms of contacts, participants, members, etc.
  
  I have seldom seen any recent install of CiviCRM (on Drupal 7) running well on anything less than 1 gig, and I always recommend at least 1.5 gig; usually 2 gig.
  
  Sorry, but I suspect no amount of MySQL tuning is going to give you what you need with only 512M.
  
  
  ---
  
  ### Answer by username_5 on 2015-08-24. Score: 0
  
  what was the version you were using before?
  
  the user interface is moving to be more reactive, and it means more smaller ajax requests than a big page loaded once in a while, it might have an impact.
  
  an issue i faced is the dashlets that tend to generate a lot of requests too, try to ask your users to remove them, see if things improve.
  
  as for the suggested size, i don't know, our servers are not vpn, so we got an order of magnitude more memory than your configuration.
  
  
  ---
  
  