If you are looking to host hundreds of small websites out of which most of them are static, then which would u consider as your server

Intel Xeon 3040 (Dual Core)
1 GB DDR Memory
250 GB Hard Drive
1,500 GB Bandwidth

or

Intel Xeon 3110 (Dual Core)
4 GB DDR Memory
2 X 250 GB Hard Drive
1,500 GB Bandwidth

Dani AI

Generated

Good call by about prioritizing memory and a second disk; that direction makes sense for hundreds of mostly‑static sites. A few additional, practical points will make the setup more robust and easier to operate as the number of sites grows.

For static hosting, disk I/O and filesystem layout matter more than raw CPU. Plan for many small files: choose a filesystem and format options that provide enough inodes, mount with noatime to reduce writes, and keep web content on a partition that can be snapshot/backed up independently from the OS. If budget allows, an SSD or hybrid tier for the webroot will reduce latency and random IOPS bottlenecks.

Serve static files with a lightweight front end (nginx or a dedicated static proxy) and use proper caching headers, pre-compressed assets, and keepalive/sendfile settings so the OS page cache is effective. Offload large or popular assets to a CDN to save bandwidth and IOPS. If any sites are dynamic, run PHP (or other runtimes) via pools or containers to isolate per‑site resources and avoid the heavyweight Apache+prefork memory use on shared hosts.

Operational basics that get overlooked: automated, incremental offsite backups with versioning and regular restore tests; per-site disk quotas to stop one site from filling the server; log rotation and centralized log retention; monitoring (open files, inode usage, disk I/O, memory, network) and alerting; and load/testing before going live. These measures protect uptime and make scaling far less painful as the count of sites increases.

Recommended Answers

All 3 Replies

If you are looking to host hundreds of small websites out of which most of them are static, then which would u consider as your server

Intel Xeon 3040 (Dual Core)
1 GB DDR Memory
250 GB Hard Drive
1,500 GB Bandwidth

or

Intel Xeon 3110 (Dual Core)
4 GB DDR Memory
2 X 250 GB Hard Drive
1,500 GB Bandwidth

Hello,

I would go with this system:

Intel Xeon 3110 (Dual Core)
4 GB DDR Memory
2 X 250 GB Hard Drive
1,500 GB Bandwidth

4GB of memory will be enough to keep Linux from having to use the swap partition and mirrored hard drives gives you redundancy for hard drive failures.

Yes, i have gone with the second config.. and have asked my provider to make the second drive as the backup one.. is it the same as mirrored?

Mirrored means that everything that is written to the first drive is written milliseconds later to the second drive. It is like having a continuous backup that is current up to the second. This way if the first drive fails the second drive is an exact copy. You lose a little speed when writing to the drives due to accessing both drives but you gain in the fact that if a drive fails you have little or no down time.
Using it as a backup disk if your primary drive fails your data is only current up to your last backup. You have to have a new primary drive with the OS installed and then restore the last backup to get your sites running again. That can take a few hours with all of the sites down. If the backup is corrupt or a week old you will have angry clients.

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.