By Paul Murray on Monday, 30 October 2017
Posted in General
Replies 10
Likes 0
Views 501
Votes 0
Hi SI Team

1) The standard mail from Site Ground

We would like to inform you that your account finalbug.net has exceeded the allowed daily program and script executions per account and your web service has been limited for the calendar day. The limit will be removed automatically at 00:10 a.m. CDT tomorrow and service will be fully restored.


2) After asking Site Ground what is going on

I've reviewed your account and the most executed script on your account is:



16485 77.179.105.249 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) Ap ...... hrome/61.0.3163.100 Safari/537.36 OPR/48.0.2685.52


Please advise what is going on here!!!

thanks

Paul
Hey Paul,

The polling.php is a much simplified version of checking for notifications and it reduces almost 90% of the load. You have 2 choices currently:

1. Reduce the polling interval time under Settings > General > Notifications to a higher value, e.g: 30 seconds or 60 seconds.

2. Switch to a better hosting provider, https://stackideas.com/inmotion-webhosting that doesn't have such ridiculous restriction.
·
Monday, 30 October 2017 11:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

Thanks for the tips.
I have increased the polling interval to 60 seconds.

1) I will write to S********d and ask them to increase these restrictions with out them trying to upgrade me
2) And in the long run I will probably move to the hoster you suggested.

Out of curiosity does this have something to do with the 2.1 update?

thanks for your fast response

Paul
·
Monday, 30 October 2017 14:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Paul,

Yep, it has something to do with the changes in 2.1. With 2.1, we try to get as real time possible with shorter polling interval by using less cpu. In order to achieve that, we need to first reduce the processing power that is used. The total reduction of CPU load in 2.1 is about 75% lesser. This is why polling.php is used instead of routing through Joomla.

In EasySocial 2.0, the polling were done every 45 seconds and this also means that if you have a friend request, you don't get instantaneous notification unless the next notification kicks in.

With the help of polling.php, we get to poll the server more frequently and it only uses a fraction of the cpu. Hence, running it a million times, would never hurt the CPU in any way.

Having said that, your hosting provider only allows 40,000 processes per day including css and js requests (As what I have been told by another customer, James Helms) This also means that, you can have a maximum visitors of up to 40,000 per day assuming that your css and js isn't a separate process.

It is a ridiculous restriction but I can see why Siteground is restricting this. It is mainly because you are only paying them a fraction of the cost of the server and in order for them to be able to maintain this, they need to charge you more.
·
Monday, 30 October 2017 15:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Mark

Thanks for all the info.

we try to get as real time possible

I understand.
More years ago than I care to remember "Real Time" was the battle cry in the world of video editing.
At the very latest when my site is running on mobiles with 100s of real time visitors this will be mission critical.

I will write to my current hoster and ask them about the:

40,000 processes per day including css and js requests


Obviously I will not mention any names as it is a small planet that we live on and you never know.

thanks again

Paul
·
Monday, 30 October 2017 15:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Paul,

No problem I got those details from James, I believe you seen him around the forums too but I am unsure if his limit is different than yours as I am unsure of the package you guys are on.

Either way, I think you should consider switching to https://stackideas.com/inmotion-webhosting . They guarantee that their hosting accounts work fine with our products.
·
Monday, 30 October 2017 16:01
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post