Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You could have a look at getting some benchmark figures to see what kind of load/traffic your current setup (infrastructure and appplication) can handle e.g. how many concurrent users etc.</p> <p>You could do this possibly using Microsoft Team Foundation Service (hosted in the cloud, different to TF Server which is hosted on premise i.e. your infrastructure. using the <strong><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/26/load-testing-with-team-foundation-service-launching-preview-and-early-adoption-program.aspx" rel="nofollow">Load/Stress/Performance tests</a></strong></p> <p>I believe TFS Service is free for a dev team smaller than 5 developers I think. Dont quote me on that :-)</p> <p>Once you get some ball park figures and if your application can cope then nothing to do. If it cant then some decisions to make? Your then in the 80/20 scenario. Is it worth spending 80% of your resource (dev time, wages etc) on a possible 20% performance gain or is it better to invest 20% hardware cost (CPU, RAM, another server etc) for an instant 80% performance boost?</p> <p>If this site is high profile for your business or customer and is generating income or has legislative purpose then you may find an invest in hardware easier then investment in software development. That way you can look to have an high-available (HA) scalable application without a single point of failure (SPF).</p> <p>Not really answering your queueing questions but just another viewpoint to consider.</p> <p>FYI we are hoping to upgrade to two VMs (running VMWare) front end webservers running windows server 2012 enterprise edition. These will be network load balanced using microsoft NLB (so no need for another load balancing server or third party software). We will have an active-active cluster for the backedn SQL servers. this allows us to maintain the servers (upgrades, patches etc) without having downtime. AN additional benefit is with IIS 8.0 you can run multiple domain (hosts) of the same IP for SSL (HTTPS) traffic using SNI which is nice (but torpedos user running windows xp but its out of support in April 2014 anyway). We have to upgradeour .net applications to take care of session management and MACstate(cross server postbacks etc) but the trade of is worth it.</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