Note that there are some explanatory texts on larger screens.

plurals
  1. POWindows Azure Extra Small Instance Harddisk Size
    text
    copied!<p>We have a Windows Azure Web Role on two extra-small instances that has been running for weeks without problems. This morning, we unintentionally passed some spending limit, which resulted in Windows Azure shutting down our complete service, without any prior warning!</p> <p>We removed the spending cap and began to re-deploy the Web Role, with the same codebase that has been running for weeks. To our astonishment, we got the deployment error</p> <p><code>Validation Errors: Total requested resources are too large for the specified VM size.</code></p> <p>We upgraded the deployment to two small instances instead of the extra-small instances, whereupon deployment was working again. Now, the web role is back in the web.</p> <p>However, we still don't understand <strong>why our deployment was suddenly too big for an extra-small instance</strong>. We didn't change one bit since the last successful deployment to extra-small instances. We then tried to remove the deployment size by moving some files to Azure Storage, but even after reducing the package file by more than 1 MB, deployment still failed.</p> <p>The <code>cspkg</code> file, the deployment package, is currently at <code>9'359 KB</code>. If unzipped, the complete <code>sitesroot</code> folder's size is <code>14 MB</code>. Which is way below the <code>19'480 KB</code> limit for the x-small instance.</p> <p>Before we lose more time with trial-and-error, here's my question: <strong>How exactly are those <code>19'480 KB</code> calculated? Is it just the <code>sitesroot</code> folder, or the zipped package, or is it the <code>sitesroot</code> and <code>approot</code> folder together, or the whole unzipped package?</strong></p> <p>Thank you!</p> <p><strong>EDIT:</strong></p> <p><img src="https://i.stack.imgur.com/gj173.png" alt="enter image description here"></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload