How do you justified your linux home based webserver's capabilities?
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I always do read those linux thread by saying that the old system is good enought to run a web base server using Linux.
But, I'm curious if there is any linux software or web base system which I can use to find out the this system's "capability" such as: "when currently there are 300 people viewing the thread in my home based webserver BBS, the system or network broadband is already reaching it's top performanace or bottleneck??
Or there are some way else i can study my system capabilities??
I think the answer to the question asked is "obviously not". The capability of your hardware as a web server depends so heavily on the way that you choose to code the website that I don't see how this is possible without making quite unjustified assumptions about how much work the system has to do for each visitor. And, even then, something else like your link to the internet (or your isp's throttling policy, which is the same thing in a way) could be the bottleneck.
So if, for example, your machine just serves up a selection of a few plain web pages that are simply requested by url, that is probably quite easy and your hardware can cope with a reasonable number of visitors, and that possibly increases with a reverse proxy in httpd accelerator mode. If every query is actually a database look up and pages are composed on the fly, then that number may well decrease by an order of magnitude. If the database code/structure is bad (inappropriate) then that number may well diminish significantly as well.
More usefully, you can build a prototype system and observe the scaling as certain numbers of users (real or simulated) access the system. This requires a certain amount of intelligence in understanding users, what they are likely to do on your site and understanding the limitations of your hardware, but it is at least in priciple 'do-able'.
Not quite sure how this relates to 'justifying' the hardware, unless you mean that you want to justify the purchase of more capable hardware.
I ran the website for my county library on a box with roughly those specs (it was a stock dell dimension 1100). The server ran for 2 years on Debian sarge, never had a problem. The site was basically html, with some downloadable pdf files and lots of pictures, so it wasn't much of a chore as far as doing a lot of php or database work. But it also ran DNS off and on, and we aren't a small county, so I'd say those specs will get you a good long way.
Like the previous poster said, I don't think you'll be able to get hard numbers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.