title: Azure Web App - Web Service best practice for running exe
body: <p>I'm facing a problem with a Web Service that uses a .exe file to produce his response.</p>
  
  <p>Actually the service is working with a simple "Process.Start" of the .exe file with the correct parameters.</p>
  
  <p>Everything works smoothly but I have this "problem". Being one of the parameters a HUGE file of 1GB the system takes 15secs to load this file EVERY request in memory.</p>
  
  <p>This file is ALWAYS the same, open in read only.</p>
  
  <p>How can I let the system know to maintain it in memory?</p>
  
  <p>I can basically follow different approaches:</p>
  
  <ul>
  <li>Find a way to say to the system "keep this file in RAM"</li>
  <li>Embed the .exe in something like "loop for input" (and use always the same process)</li>
  <li>Publish the exe as a Continuosly running Azure Web Job</li>
  </ul>
  
  <p>Before trying out every approach on my own, what is the best approach and why?</p>
  
  <p>Thanks in advance</p>