tag:help.appveyor.com,2012-11-13:/discussions/problems/24776-visual-studio-2019-image-significant-queuingpending-delaysAppVeyor: Discussion 2019-10-16T21:01:27Ztag:help.appveyor.com,2012-11-13:Comment/475303082019-08-15T20:10:52Z2019-08-15T20:10:52ZVisual Studio 2019 image - significant queuing/pending delays<div><p>All builds running on a Visual Studio 2019 image are taking 4-5 minutes to be assigned and start building. Previous images like Visual Studio 2017 were only taking 10-15 seconds to start building.</p>
<p>This is causing pretty significant delays since we're often running multiple deployments per day.</p></div>jristinetag:help.appveyor.com,2012-11-13:Comment/475303082019-08-15T21:47:32Z2019-08-15T21:47:32ZVisual Studio 2019 image - significant queuing/pending delays<div><p>It's important to differentiate <strong>queue time</strong> vs. <strong>start time</strong>. You can read about the difference <a href="https://www.appveyor.com/docs/build-configuration/#build-queue">here</a>.</p>
<p>If you have other projects building and your plan has only one concurrent build, then new builds will have to be queued.</p>
<p>Regarding <strong>start time</strong>, currently VS 2019 image builds are run in azure but we plan to move them to Hyper-V later at which point VM's will be kept "pre-heated" and start up time will be reduced.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/475303082019-08-16T13:28:15Z2019-08-16T13:28:15ZVisual Studio 2019 image - significant queuing/pending delays<div><p>I'm referring to the start time, and that explanation makes sense. Can you share an estimated timeline for when the move to Hyper-V will occur?</p></div>jristinetag:help.appveyor.com,2012-11-13:Comment/475303082019-08-16T18:44:55Z2019-08-16T18:44:55ZVisual Studio 2019 image - significant queuing/pending delays<div><p>We plan to do it this calendar year. Sorry for now being more specific.</p></div>Ilya Finkelshteyn