Answers.Body: <p>As others point out, there are no clear answers. The number of simultaneous users is also an important factor. But here are some tips from my administration of a similarly-sized database:</p>
  <ul>
  <li>I run everything on a 4GB server.  This is usually sufficient, but when my client had a very high-traffic event, I saw some monitoring warnings (though I couldn't detect slowdown in manual testing).  If you're eligible for Microsoft Azure free hosting credits, you can get an 8GB server and not worry*.</li>
  <li>Local vs. cloud doesn't affect performance.  If &quot;local&quot; implies &quot;not accessible to the Internet&quot; that will mean you lose some features though.</li>
  <li>Install Redis.  I have it on my live site but not my dev site and the difference is noticeable.</li>
  <li>Tweak your MySQL settings to give as much InnoDB cache as you can spare.</li>
  </ul>
  <p>* As Alan points out in the comments, there are many political reasons to not host with Microsoft; data privacy issues, jurisdiction and a willingness of your host to fight for your rights are all important.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-16T19:17:16.777Z
Answers.Text: I agree that memcached (or redis) makes a big difference to the admin and authenticated user experience, I'd always recommend it. I would assume that you'll want to replace your server about every 3 years for various reasons (i.e. include that assumption in your planning, even if you don't actually do it). I also think that hosting is a political choice, especially these days.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-11T15:01:00.300Z
Answers.LastActivityDate: 2021-02-17T00:13:34.383Z
Answers.LastEditDate: 2021-02-17T00:13:34.383Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>New here and a few months ago we start working with Civi for a small project but now we are planning to use it for a project with a over 300.000 contacts and 40+ users. I would like some help and suggestions :</p>
  <ul>
  <li>What is the ideal Civi setup for a large project like this ?</li>
  <li>Shoud we use wordpress or drupal ?</li>
  <li>Local or Cloud hosting ?</li>
  </ul>
  <p>Thank you in advance.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-02-10T19:15:39.350Z
Comments.Text: Those are some pretty wide open questions with subjective answers. Ultimately more resources are always better for big datasets in any environment. That can be done with any of the choices you offer. This forum is typically for questions that have clear answers. I'm afraid there are no definitive answers for these questions.
Comments.UserDisplayName: kapn
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-02-11T07:54:59.170Z
Comments.Text: The number of contacts do not necessarily have the most impact on performance, other tasks (e.g. complex smart groups) may be more of an issue. That being said, we would probably use a server with 4-8 GB of RAM and 2-8 cores (as kapn said, more is better) and it should definitely have an SSD and not an HD. WP or Drupal probably would not make a lot of difference.
Comments.UserDisplayName: Fabian
Tags: <wordpress><drupal>
Title: Ideal Civi Setup for big database
ThreadText: # Ideal Civi Setup for big database
  
  (Asked by: username_0 on 2021-02-10)
  
  New here and a few months ago we start working with Civi for a small project but now we are planning to use it for a project with a over 300.000 contacts and 40+ users. I would like some help and suggestions :
  
  * What is the ideal Civi setup for a large project like this ?
  * Shoud we use wordpress or drupal ?
  * Local or Cloud hosting ?
  
  Thank you in advance.
  
  **Tags:** wordpress, drupal
  
  > **Comments:**
  > **username_1**: Those are some pretty wide open questions with subjective answers. Ultimately more resources are always better for big datasets in any environment. That can be done with any of the choices you offer. This forum is typically for questions that have clear answers. I'm afraid there are no definitive answers for these questions.  
  > **username_2**: The number of contacts do not necessarily have the most impact on performance, other tasks (e.g. complex smart groups) may be more of an issue. That being said, we would probably use a server with 4-8 GB of RAM and 2-8 cores (as username_1 said, more is better) and it should definitely have an SSD and not an HD. WP or Drupal probably would not make a lot of difference.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2021-02-11. Score: 1
  
  As others point out, there are no clear answers. The number of simultaneous users is also an important factor. But here are some tips from my administration of a similarly-sized database:
  
  * I run everything on a 4GB server. This is usually sufficient, but when my client had a very high-traffic event, I saw some monitoring warnings (though I couldn't detect slowdown in manual testing). If you're eligible for Microsoft Azure free hosting credits, you can get an 8GB server and not worry\*.
  * Local vs. cloud doesn't affect performance. If "local" implies "not accessible to the Internet" that will mean you lose some features though.
  * Install Redis. I have it on my live site but not my dev site and the difference is noticeable.
  * Tweak your MySQL settings to give as much InnoDB cache as you can spare.
  
  \* As Alan points out in the comments, there are many political reasons to not host with Microsoft; data privacy issues, jurisdiction and a willingness of your host to fight for your rights are all important.
  
  > **Comments:**
  > **username_4**: I agree that memcached (or redis) makes a big difference to the admin and authenticated user experience, I'd always recommend it. I would assume that you'll want to replace your server about every 3 years for various reasons (i.e. include that assumption in your planning, even if you don't actually do it). I also think that hosting is a political choice, especially these days.  
  
  ---
  
  