Answers.Body: <p>I have been doing this a lot recently. My iOS Syzygy 6-men apps require at least 2GB (possibly more) to run, which is not so easy for iPhones and iPads.</p>
  
  <ul>
  <li>You gain the most benefit if you follow <a href="https://shop.chessbase.com/en/products/endspiel_turbo_4" rel="nofollow noreferrer">https://shop.chessbase.com/en/products/endspiel_turbo_4</a>. This is also how I distribute.</li>
  <li>Stockfish only memory map (mmap) your tablebase file when it is needed. So you might choose your files depend on what position you want.</li>
  <li>I can't comment on iSCSI, NAS etc.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-23T14:41:54.633Z
Answers.LastActivityDate: 2017-01-23T14:41:54.633Z
Answers.UserDisplayName: SmallChess
Answers.Body: <p>During search engines access the *.rtbw files only. These are best placed on your fastest local drive (ca. 70 GB). Low latency is more important than bandwidth.</p>
  
  <p>The *.rtbz files are not speed critical. They are needed at the root only, when playing out 6-man positions.</p>
  
  <p>The caching is best left to your OS.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-28T05:12:02.283Z
Answers.Text: All engines supporting Syzygy require the files be in the same physical path.
Answers.UserDisplayName: SmallChess
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-11T22:38:30.867Z
Answers.Text: Most allow specifying multiple paths, for example separated with `:` in Stockfish.
Answers.UserDisplayName: Niklas
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-27T20:34:10.063Z
Answers.LastActivityDate: 2017-01-27T20:34:10.063Z
Answers.UserDisplayName: Queeg
Body: <p>I have downloaded a copy of the 6 man Syzygy tablebase and configured it on my Fritz 15 GUI. </p>
  
  <p>Due to obvious memory constraints, the full 6 man Syzygy tablebase cannot be loaded into memory (ie. ramdisk). Will I gain any benefit moving some of the 6 piece tablebase files onto a ramdisk, and if so, which piece combinations should I gain the most benefit from (ie. in terms of endgame positions). Has anyone done analysis in this area?</p>
  
  <p>Currently I host my 6 piece Syzygy tablebase on my Synology NAS via iSCSI. </p>
  
Tags: <engines><tablebases>
Title: 6 man syzygy tablebase and ramdisk
ThreadText: # 6 man syzygy tablebase and ramdisk
  
  (Asked by: username_0 on 2017-01-23)
  
  I have downloaded a copy of the 6 man Syzygy tablebase and configured it on my Fritz 15 GUI.
  
  Due to obvious memory constraints, the full 6 man Syzygy tablebase cannot be loaded into memory (ie. ramdisk). Will I gain any benefit moving some of the 6 piece tablebase files onto a ramdisk, and if so, which piece combinations should I gain the most benefit from (ie. in terms of endgame positions). Has anyone done analysis in this area?
  
  Currently I host my 6 piece Syzygy tablebase on my Synology NAS via iSCSI.
  
  **Tags:** engines, tablebases
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-01-23. Score: 2
  
  I have been doing this a lot recently. My iOS Syzygy 6-men apps require at least 2GB (possibly more) to run, which is not so easy for iPhones and iPads.
  
  * You gain the most benefit if you follow <https://shop.chessbase.com/en/products/endspiel_turbo_4>. This is also how I distribute.
  * Stockfish only memory map (mmap) your tablebase file when it is needed. So you might choose your files depend on what position you want.
  * I can't comment on iSCSI, NAS etc.
  
  
  ---
  
  ### Answer by username_2 on 2017-01-27. Score: 1
  
  During search engines access the \*.rtbw files only. These are best placed on your fastest local drive (ca. 70 GB). Low latency is more important than bandwidth.
  
  The \*.rtbz files are not speed critical. They are needed at the root only, when playing out 6-man positions.
  
  The caching is best left to your OS.
  
  > **Comments:**
  > **username_1**: All engines supporting Syzygy require the files be in the same physical path.  
  > **username_3**: Most allow specifying multiple paths, for example separated with `:` in Stockfish.  
  
  ---
  
  