title: How much faster can web-workers make my browser game?
body: <p>I am making a browser game, and am wondering what types of performance improvements I could expect from web workers.</p>
  
  <p>Refactoring would not be an issue, my code is already set up with this in mind.</p>
  
  <p>Some have said that using web workers has made their game have 10-100x better performance -> <a href="https://www.quora.com/Are-web-workers-useful-for-JavaScript-games" rel="nofollow noreferrer">https://www.quora.com/Are-web-workers-useful-for-JavaScript-games</a> </p>
  
  <p>I would only instantiate a pool of 8 web workers because that is the most I imagine to be necessary with my computer's 8 cores. Any more than that and it would provide no performance boost (Or would it for some reason?). </p>
  
  <p>Given a little overhead from web workers and assuming bottlenecks are evenly spread, (graphics is not a bottleneck) this would typically leave me to expect about 7x performance when using web workers.</p>
  
  <p>Or would it be the case that having graphics and logic on different intervals but the same thread reduces your performance to the extent that adding in 7 more threads could lead to 10-100x performance boosts?</p>
  
  <p>Maybe it is the case that web workers are just not right for this quick game interval (50 ticks per second). And even if they did work it would only bring me improvements totaling 2x?</p>
  
  <p>It will take some work to Integrate web workers, what should I expect in the end?</p>