Web Development

See this thread, install the programs and post the results:

https://www.unix.com/web-programming-...#post302220677

Also, post your apache2.conf and my.cnf configuration files, plus post your OS, stats (RAM, CPU) and the output of top, etc.

Neo,

I was trying to do some "manual" benchmarking with Apache's flood, but even though I have two instances with 100 threads each, it causes only 4 slave servers to go into the "run" state. Do you know of another tool for load testing?

The only way we can accurately tune this site is on the live traffic over many days. I don't think it is really possible to tune performance very well with tools that flood a server with traffic. I did run ab a few times, but it is really a waste of time. Here is the link:

ab - Apache HTTP server benchmarking tool - Apache HTTP Server

The trouble is that tuning requires setting many parameters over time, like key buffers, query cache, timeouts, max connections, etc. So many parameters and each parameter is different.

I noticed the other day that someone ran a flooding tool against this site, because we reached maximum connnections, which only happens when a flooding tool is used :-) Please do not do this. Why? Because it completely ruins the tuning analysis. Flooding is not real traffic and it is not even close to helpful.

In other words, what happens with flooding tools is so different than with real world LAMP.

There is some good reading on the net, for example:

Tuning LAMP systems, Part 3: Tuning your MySQL server

But even these recommendations are only useful as background reference, because each site is different, the hardware is different, the traffic is different, the database queries are different, the JavaScript is different, etc etc.

I used to read all of these, and they are useful; but at the end of the day, LAMP tuning is based on knowing the system details, hardware, software, database structure, traffic pattern, query pattern, load etc. Tools cannot come close to simulating the real traffic (load, queries, timeouts, dropped connections, etc), especially on a site like this.

I post in the wrong thread but can't delete my post !!

Sorry.

No that was the good one but sone post came in i didn't see before.

I manage to prevent system from crashing out of swap with mpm tuning.

I am still not happy with these typo3 page but I guess I cant do so much from system point of view.

Thanks all for your good advices.

PS : I use mysql tuning-primer.sh and it looks happy with my config.

If the typo3 page is the same for most users and does not depend on session-specific or IP-specific data, I think squid will help. Like I said, you can use mod-rewrite to go to squid if there's session/cookie data, and to typo3 if there isn't.

Glad you're not crashing, anyway

Don't forget to also run mysqltuner.pl

Normally, I run both and compare the results.