300 processes running at the same instant, all of which were "index.php" scripts

Permalink
Apologies this is probably not the right forum but I did not see a place for server related issues. Which it should be noted this is first time I have encountered in 3 years of using C5. How seldom I have had to use these forums is the highest praise I can offer C5 :)

So I got one of those pesky website is running a large
number of server processes notifications from a clients host. The site is low traffic and should not be really creating a load. I have numerous other C5 sites with this host and never had a problem.
Upon further investigation the host pinpointed the problem as: " it looks like there were over 300 processes running at the same instant, all of which were "index.php" scripts. This tends to suggest that the site was being visited a large number of times in a short space of time"

Now the site receiving a large number of visits was strange in itself and I have blocked some clearly "shady" IP's from returning.
So I suppose end question is 300 instances of index.php is unusual?
It is likely a caching issue?
As such turning off page caching should dramatically limit the impact this recurring or a higher traffic volume has?

My immense gratitude to anyone who has the time to reply or inclination to share their input. Apologies if its in wrong forum or I am being a complete air head :)

 
JohntheFish replied on at Permalink Reply
JohntheFish
index.php is the entry point for any interaction with the c5 core. Within a c5 page, there can be lots of components that are delivered through index.php, not just the actual page. Ajax requests, internationalisation, some files, anything in an iframe. Some core actions (automated jobs) and addons make further page requests within a page while it is still being evaluated on the server. ..... So your 300 could be considerably fewer than 300 actual visitors. Then each visitor may open several browser tabs open at the same time.

Even so, 300 does seem a bit high. When a site is crawled by a robot (such as google) you could expect higher than normal, but robots are designed not to grab everything in one binge.

Caching is unlikely to have anything to do with it.
slowdive replied on at Permalink Reply
Thanks so much for taking the time to reply. The site has been up on this server for some months and active development prior with no issues. So I am going to assume/hope it has something to do with the now blocked IP's.
If the issue repeats, I will have to find out more about environment actual footprint and greater detail and lean on the community again.

Much appreciated, thanks for your time responding.