Maximum volume of AJAX requests allowed

[Oxy]

@GentooUser

Script Usage Terms
Scripts on the site must be designed to produce web-based content, and not to use the server as an application server.

But due to server-side scripting languages like PHP, the distinction between a web server and application server is fuzzy.

Yes - it is debatable (if you are looking at only one item from TOS and not as a whole)

Because you can make your website use a microphone
and depending on the decibel level, your PHP script in the background generates 3D images as a background image for your web page and this is refreshed quite often

what I mentioned is web-based content

But that simply exceeds the possibilities of the free hosting service because it simply consumes too many resources and can be interpreted as abuse

you will probably see 508 errors in the console log first

What is an Entry Process and what does the limit mean

One of the limits InfinityFree enforces is the Entry Process Failures limit, also abbreviated to Entry Process limit or EP limit. This article explains what an entry process is, what the limit means and how you can control it. What is an entry process? Every time a request to a URL on your website is made, a new program is started to retrieve the content of that URL. This process then executes your code, sends the response to the visitor, and finally quits. Note that one entry process is creat…

@Admin

In general, every request made from a visitor’s browser that hits a PHP script on the server uses some server power. Server power is a finite resource, so we limit how much you can use. And since we provide a free service, the limits are not very high.

The question “how much AJAX is too much AJAX” is impossible to answer for all sites. It really depends on how your website was built, how many people use it, and how often you query the server.

You’re free to use AJAX on your website. Just don’t try to host an application that rapidly polls the server for updates, like a chat script, with us, because you’ll quickly hit limits.

@Admin

It may sound unfair, but this is how it works on all types of hosting. Every request made against a website requires processing power to run. That processing power is taken from your hosting account quota, or the total capacity of the server(s) you own. Of course it would be nice to not have to spend your server power on such requests, but it’s hard to tell such traffic apart.

@Admin

Long story short, your website takes too much processor power. When you hit the processing power limits, your account will be suspended for 24 hours. However, if this happens very often, it simply means that your website consumes too much processing power. If that’s the case, the best choice would be to upgrade your account, because you’ll get far more processor power there.

We use two different metrics to measure CPU usage. We track the number of CPU seconds you use, displayed as CPU limit, and the number of entry processes, abbreviated as EP.

The number of CPU seconds is the number of seconds you are consuming one full processor core to calculate the pages on your website. This is scaled to how much of the processor you use, so 1 second of 20% core usage is 0.2 CPU seconds. This mostly has to do with how much work needs to be done to render a specific page.

Entry processes are the number of PHP processes which are created to render your website. Simply put: every time a request is received for a PHP page, a new process is created for your user. This is what’s known as an Entry Process. The number of entry processes has to do with the number of page views your website receives.

In your plugins list, I see you’re using an Ajax Shoutbox. Does that plugin updates posts in real time? If so, that’s considered a chat script, which are prohibited because they consume so much server power.