Member Avatar for Duki

Hey everyone, I'm not sure where to post this so feel free to move if needed.


A fellow classmate and myself are starting on message board project. I was asked to spec a powerful windows based system, but am unsure of what is most important in a web server?

Could someone point me in the right direction?

Thanks! :mrgreen:

  • 6 Contributors
  • 7 Replies
  • 92 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

Short, practical plan for a Windows-based message board (answers below tie into points made by , , , , @GCS584 and ):

Start by defining the workload: peak concurrent users, read:vwrite ratio, attachments, search, SSL and any server-side processing (image resizing, spam checks, etc.). These characteristics determine whether the site is CPU-bound, I/O-bound, or memory-bound. Small, low-traffic boards can run on minimal hardware; larger or database-heavy boards need a different balance.

Architecture and tuning priorities: separate web and database tiers once you expect moderate traffic. Place database files and logs on storage with high IOPS (SSDs; RAID10 for write-heavy). Allocate and tune DB server memory rather than just letting the OS decide—see Microsoft guidance on SQL Server memory configuration for specifics (). Use connection pooling, index queries, and add an in-memory cache or output caching to reduce DB load (). Offload static assets to a CDN and enable compression and HTTP keep-alive to reduce CPU and bandwidth pressure.

Measure before you buy. Instrument IIS and Windows perf counters (CPU, Available MBytes, Disk Queue Length, Avg disk sec/Read/Write, Network bytes/sec), and use SQL profiling to find slow queries. Run realistic load tests (JMeter/ab) and iterate: optimize queries and caching first, then add CPU, memory, or faster disks as needed. If a bottleneck appears, scale horizontally (additional web nodes behind a load balancer) rather than over-provisioning one box.

Checklist: estimate peak concurrency, separate web/DB for growth, tune DB memory, add caching and CDN, use SSDs/RAID suited to writes, monitor with perf counters, and load-test early. The posts in this thread show both extremes: tiny servers can work for tiny forums (), while DB- or CPU-heavy features change the hardware priorities (, ). Let measured metrics guide the final spec.

Recommended Answers

All 7 Replies

Member Avatar for Dani

RAM and the speed of the hard drives???

Member Avatar for Duki

alright, so CPU isn't a big factor when specing out a web server?

Member Avatar for manofgames

Well, I'd imagine it is actually, after all if a cpu is the computer's 'brain' then there's no point giving a supposedly suped up server a tiny amount of processing power.

Member Avatar for jbennet

i disagree

I run a web server happily on 128mb ram and 2x 233mhz pentium IIs

Main thing is fast HDDs / NICs and reliable

Member Avatar for Member #114857

Well, I'd imagine it is actually, after all if a cpu is the computer's 'brain' then there's no point giving a supposedly suped up server a tiny amount of processing power.

manofgames is almost quite correct in his statement. There are many factors that will ultimately determine the performance of a web server. A web server utilizes a vast amount of hardware components. Ultimately, a bottleneck in a single component can drastically affect your overall web server's performance.

What hardware you require will depend on how you are using the site and how many visitors you expect to serve.

As per Apache's page on 'Apache Performance Tuning', "The single biggest hardware issue affecting webserver performance is RAM." It carries on further and says, "Beyond that the rest is mundane: get a fast enough CPU, a fast enough network card, and fast enough disks, where 'fast enough' is something that needs to be determined by experimentation."

GCS584

Member Avatar for brit

It depends what kind of pages do you want to host. If you don't serve databases, then cpu could be not so much important, but in any other case, better be prepared for 'heavy' sites.

Member Avatar for jbennet

256+ ram is needed for SQL unless you want to get errors

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.