Portal Home > Knowledgebase > Articles Database > Do you allow 1 hr max php exec time?
Do you allow 1 hr max php exec time?
| Posted by Tomcatf14, 08-15-2012, 01:26 PM |
| on a shared server. One of my client need 1 hr php execution time to run his script as recommended by the developer. I find this is too long
|
| Posted by Zachary McClung, 08-15-2012, 01:34 PM |
| That does seem like a long time to be executing a script. That comes down to a business decision on whether the risk is worth the reward.
|
| Posted by Tomcatf14, 08-15-2012, 01:38 PM |
| The money is good as this is a Semi-D account. I only squeeze small amount of client in the server and selling it at a high price.
But allowing 1 hr PHP exec in a shared server is beyond what I have done for the past 10 yrs
|
| Posted by Server Management, 08-15-2012, 01:46 PM |
| Kindly ask him to use a VPS or Dedicated server for this...
Execution time is normally rather seconds/minutes not hours.
The default execution time within cPanel is 90 seconds for example.
Last edited by Server Management; 08-15-2012 at 01:49 PM.
|
| Posted by cenourinha, 08-15-2012, 02:43 PM |
| I don't see why would your customer need 1 hour to execute a script. If you allow this on a shared server, you will put all your other customers on risk.
|
| Posted by brianoz, 08-16-2012, 06:12 PM |
| Quite likely this code hasn't been optimized at all, and is either doing some poorly coded SQL tasks, or something that just takes way too long.
Some developers don't explore options well; and this is just way too long for a script to run. They need to think about what they are doing.
|
| Posted by racknap1, 08-21-2012, 12:21 PM |
| Hi,
This is the same case with a particular megento installation on a dedicated server, At that time megento was in need of mcrypt and php max execution time with 18000.
In that case we had altered /etc/php.ini with :-
max_execution_time = 18000
And install mcrypt on server manually and restarted Apache.
30 days passed, and site is running absolutely fine.
|
| Posted by racknap1, 08-21-2012, 12:23 PM |
| But one more thing, I don't think your hosting provider would allow this much of max execution time = 24 hours.
Your should get your own server to implement that.
|
| Posted by BestServerSupport, 08-21-2012, 12:34 PM |
| Shared Hosting Provider will not allow this much long amount of time for script execution. It may create big issues to their other customers websites. If you have a VPS OR dedicated server then only I would recommend to set it.
|
| Posted by mSuleman, 08-21-2012, 01:45 PM |
| on shared hosting i think so never ever and same as other described on vps and dedicated server will work.
|
| Posted by KMyers, 08-21-2012, 01:59 PM |
| The danger of this is that this is a global change. It means that one customer could in theory take down the server with a massive database query.
|
| Posted by prashant1979, 08-22-2012, 12:00 AM |
| On a shared hosting server, it is a strict No-No. Better ask your customer to optimize the code or opt for a dedicated server or a vps. Optimizing the code would be a safe bet as even a vps or a dedicated server may have load issue if the code execution takes that much time.
|
| Posted by ArturasLIX, 08-22-2012, 03:44 AM |
| For shared hosting it's normal to have values in range 30 - 120 seconds. For greater values the best solution is to have VPS server with dedicated resources.
|
| Posted by nehir, 08-22-2012, 04:49 AM |
| it's probably a BOT script.. (IRC Bot, Search Bot etc..)
or MySQL based backup/restore script..
Do not allow it on a shared server..
|
| Posted by racknap1, 08-22-2012, 12:42 PM |
| Hi Tomcatf14,
Get a dedicated or semi-D for it, nothing less.
|
| Posted by Hillockhosting, 08-24-2012, 01:51 AM |
| Allow max upto 300
Anything above that would not keep the server in optimal mode
|
Add to Favourites 
Print this Article
Also Read
if isset (Views: 763)