PHP+MySQL: How much traffic?

[gerardg]

Just a rough estimate, how much traffic would you expect PHP+MySQL to be able to handle with:

• a amd/intel server in the 1ghz range.
• About 10 queries/page - all optimized/indexed, etc. Pages are pretty basic - just spit out data w/o much processing.
• 1 in about 100 pages also has about 10 inserts/updates.
• 512 MB? 1GB ram?
• 10 tables, most with 1's/10's of rows; 2 with 1,000 to 10,000's of rows (maybe one will get up to 100K+ rows).

[Anon]

it depends on your band-width
and how you've written your code

[[deleted]]

Impossible to say, what you consider 'pretty basic' could mean 'very complicated' to someone else.

The easiest way to find out is to hit your server with a very high load and see if it keeps up. (doing a benchmark on one request is useless because that just tells you how fast the server can give you one page at a time, in real life you'll get many concurrent requests, which a single-cpu machine doesn't handle well)

One thing to note though: MySQL without InnoDB will seriously slow down inserts on the 'larger' tables due to forced table-level-locking.

[gerardg]

The easiest way to find out is to hit your server with a very high load and see if it keeps up.<

How so? Apache's ab tool, a script using 'wget', or ...?

[[deleted]]

Whatever tool you like. AB is good because it gives you a nice report about it's findings.

Just remember to use a second PC, don't run AB on the target machine (obvious but common mistake) Also, hit it with a realistic load; many concurrent hits. It's no use to request one page 1000 times in a row, make it run 10-20 concurrent threads all fetching the same page 50 times or something.

Ideally you'd set AB up to request 20 different pages, 5-10 at a time, 20-50 times in a row.