Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm currently re-developing an ASP.NET website for a client and they want to upgrade their server hardware, but they're not sure to what.

The current server specs are: AMD Athlon 3200+ with 2GB RAM, running both IIS and SQL Server 2005.

The traffic for the existing site averages: 36,500 unique visitors and 220,000 page-views a month, and according to the client, the current server has difficulty handling the requests.

Any recommendations would be much appreciated. Thanks.

share|improve this question

closed as off topic by TomTom, EEAA, Dan, Khaled, dunxd Jan 7 '13 at 13:20

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

    
possible duplicate of Can you help me with my capacity planning? –  dunxd Jan 7 '13 at 13:20

2 Answers 2

up vote 0 down vote accepted

A bigger server? Seriously, this is a "no idea" talk. I likely would go with a higher range server and virtualize it. YOU have to tell us where the problem is. "It is slow" is like "the food is not good". You have to give details. YOU are the person with access to the machine.

You memory is quite pathetic - so more memory it is, and likely you are limited on the rest too.

Get a 4-8 core cpu (amd or intel), decent ram and enough SSD to handle the IO and you should be set quite some time.

Btw., I also vote to close - shopping questions are off topic here.

share|improve this answer
    
I just needed an approximate idea, which you've given, thank you. –  Adnan Jan 7 '13 at 12:50

Sign up for a trial and install the New Relic .net client on the current machine.

I recently took this step on a site where we had spent an awful lot of time addressing performance with caching. It turned out that we needed a set of indexes on the DB.

New Relic immediately identified the slow transaction and displayed the SQL queries that were responsible.

It displays a breakdown of what the server is spending time doing. So that you can target your improvements.


That said I agree that 2GB RAM with a web server that is running SQL and IIS is likely to be your problem.

Disclaimer: I have no connection with New Relic except using it happily myself.

share|improve this answer
    
Cool, I'll check that out, thanks. –  Adnan Jan 7 '13 at 12:51

Not the answer you're looking for? Browse other questions tagged or ask your own question.