Answers.Body: <p>It's a little bit hard to answer without more info but generally the ram disk isn't going to save your data unless you do something extra, so it's more useful for one-off tests or something where you need speed over permanence, like running unit tests (which it mentions in the <a href="https://github.com/amp-cli/amp/blob/v0.5.0/doc/ramdisk.md" rel="nofollow noreferrer">readme</a>). I don't use buildkit since I'm on windows but I do <a href="https://gist.github.com/demeritcowboy/9631bc0114594be10a7a75ae766baca4" rel="nofollow noreferrer">switch over to a ramdisk</a> when running tests since it's way faster when it keeps needing to load/reset the database. I wouldn't recommend a ramdisk for setting up a semi-permanent dev environment that you plan to work on regularly, unless you're willing to regularly dump the data somewhere and reload it later, or automate that at startup/shutdown, and risk losing something in the middle.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-10T22:36:13.400Z
Answers.Text: right so the ram_disk is loaded into ram and disappears when I shut my machine down. Duh on me. So, I made the wrong choice, since my goal is a semi-permanent dev environment. Back to `amp config` set up. Thanks!
Answers.UserDisplayName: Joe McLaughlin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-10T22:54:51.407Z
Answers.Text: From the readme - "The data will be wiped after rebooting or unmounting."
Answers.UserDisplayName: Joe McLaughlin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-11T19:39:15.367Z
Answers.Text: Edited the text to add more info about my intent/goal.
Answers.UserDisplayName: Joe McLaughlin
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-10T22:26:30.670Z
Answers.LastActivityDate: 2019-09-10T22:26:30.670Z
Answers.UserDisplayName: Demerit
Body: <p>I've successfully set up a <code>drupal-clean</code> test build on my Ubuntu 19.04 machine using buildkit, <code>amp config</code> and <code>amp test</code> and chose <code>mysql_ram_disk</code> rather than <code>mysql_dsn</code>. </p>
  
  <p>My intent was to have a semi-permanent dev environment. </p>
  
  <p>Did I make the wrong choice? Should I use <code>mysql_ram_disk</code> for such an environment? </p>
  
Tags: <mysql><civicrm-buildkit>
Title: Is it 'better' to use mysql_dsn rather than mysql_ram_disk with buildkit and amp config?
ThreadText: # Is it 'better' to use mysql_dsn rather than mysql_ram_disk with buildkit and amp config?
  
  (Asked by: username_0 on 2019-09-10)
  
  I've successfully set up a `drupal-clean` test build on my Ubuntu 19.04 machine using buildkit, `amp config` and `amp test` and chose `mysql_ram_disk` rather than `mysql_dsn`.
  
  My intent was to have a semi-permanent dev environment.
  
  Did I make the wrong choice? Should I use `mysql_ram_disk` for such an environment?
  
  **Tags:** mysql, civicrm-buildkit
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-09-10. Score: 3 | Accepted answer
  
  It's a little bit hard to answer without more info but generally the ram disk isn't going to save your data unless you do something extra, so it's more useful for one-off tests or something where you need speed over permanence, like running unit tests (which it mentions in the [readme](https://github.com/amp-cli/amp/blob/v0.5.0/doc/ramdisk.md)). I don't use buildkit since I'm on windows but I do [switch over to a ramdisk](https://gist.github.com/demeritcowboy/9631bc0114594be10a7a75ae766baca4) when running tests since it's way faster when it keeps needing to load/reset the database. I wouldn't recommend a ramdisk for setting up a semi-permanent dev environment that you plan to work on regularly, unless you're willing to regularly dump the data somewhere and reload it later, or automate that at startup/shutdown, and risk losing something in the middle.
  
  > **Comments:**
  > **username_0**: right so the ram_disk is loaded into ram and disappears when I shut my machine down. Duh on me. So, I made the wrong choice, since my goal is a semi-permanent dev environment. Back to `amp config` set up. Thanks!  
  > **username_0**: From the readme - "The data will be wiped after rebooting or unmounting."  
  > **username_0**: Edited the text to add more info about my intent/goal.  
  
  ---
  
  