June 6, 2017 at 3:39 pm
Environment Details: Windows Server 2012, SQL Server 2014 Standard Edition, DB size 78GB, 16 Cores, 96GB of RAM.
We have an event coming up in 2 months where all our paid members/subscribers log into the webpage to see details about their crops and crops from other states, who is growing what etc. It is just a 4 day event and there are 8000 subscribers who are going to perform all sort of functions to see what they need to see. We haven't tested to see if our server is capable of handling these many request. Can someone tell me the best possible way to tackle this? How do I make sure that the server won't crash like the Canadian immigration website crashed when DJT became the president.
June 6, 2017 at 4:25 pm
newdba2017 - Tuesday, June 6, 2017 3:39 PMEnvironment Details: Windows Server 2012, SQL Server 2014 Standard Edition, DB size 78GB, 16 Cores, 96GB of RAM.
We have an event coming up in 2 months where all our paid members/subscribers log into the webpage to see details about their crops and crops from other states, who is growing what etc. It is just a 4 day event and there are 8000 subscribers who are going to perform all sort of functions to see what they need to see. We haven't tested to see if our server is capable of handling these many request. Can someone tell me the best possible way to tackle this? How do I make sure that the server won't crash like the Canadian immigration website crashed when DJT became the president.
If your on a time crunch with a low or limited budget, you could try searching for free load testing tools or open source tools.
Most of the licensed products have trial periods that you could also use.
They all have differences such as scripting languages for tests, browser support, application types, etc so you probably want to start searching on different products to see what works best for your environment, needs, skill sets, etc. It sounds like load is your biggest concern but testing out other areas wouldn't hurt either - great performance with incorrect results can be just as bad as crashing.
I've used Paessler's before but it was awhile back. It was good for the ramp up connections though and it's free now:
Webserver Stress Tool
For database unit testing, tSQLt is pretty good for a free tool:
tSQLt
Sue
June 7, 2017 at 7:51 am
Thanks Sue, It looks like a decent tool which I am planning on using to test. I appreciate the help.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply