Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Dear jack96161,

    with your background you should know better. Raising memory or execution time has (of course) the potential to make security problems bigger, but it is most likely not the cause of the security problems.

    If you have any experience with the LAMP-stack and hosting WordPress with it’s inexhaustible amount of themes and plugins you will know what I am talking about.

    This tool might be unusable for you, but I strongly doubt that you are the intended clientele for this tool since system/web administrators who are managing a large amount of WordPress installations are usually not found as customers at (sorry) “low-end” shared hosting service providers.

    Sincerely,

    H =)

    dear jack96161,

    if a script needs more time to run because the task it has to handle takes longer than what is configured in your hosting providers max execution time, then your needs have outgrown your hosting providers configuration (PHP/HTTPd and/or hardware).

    Either your hosting provider is willing to let you configure and use what your site needs (or to configure it for you) or you have to move your site to another provider.

    Also (coding wise), it is not necessarily always possible and/or affordable to split tasks into small subtasks to make everything run at (low-end) shared hosting providers. This would be introducing a lot of overhead and make development a lot more time consuming, complex and expensive.

    On top of that is the hardware (or virtualization) configuration of your hosting service provider directly affecting the execution time of scripts.

    For example you will get a lot more operations within 30 seconds on a 3.5GHz CPU than within 60 seconds on a 1.2GHz CPU.

    Maximum execution time and consuming more resources (memory, processing time, whatever) is only jeopardizing your site if what you are having at hand is not sufficient for handling your sites needs.

    Raising maximum execution time or consuming more resources doesn’t mean to introduce any security risk by itself. I do not understand your concerns here.

    (Shared) hosting providers who are able to handle higher load (more simultaneous scripts and/or more execution time) are neither less competent nor less secure than your (so called) “competent shared hosts”.

    For me it sounds like you are maybe not doing (yourself and) your clients a favour if you are only recommending (low-end?) shared hosters. It’s like recommending everyone who needs a car to buy a Piaggio Ape. As you can surely imagine, not everyone will get satified with a Piaggio Ape. Different problems will result in different solutions.

    What I want to tell you is, that your point of view is maybe a little ‘limited’? No Offense!

    I hope I’ve been able to make my point clear now.

    H =)

    Your definition of “competent shared service hosts” might not be very wide spread. In my opinion, a host where I can not alter certain settings like the maximum execution time of php-scripts is either far from competent or just offering zero configurable hosting for people who do not want to spent any money on it and so lowering his costs for support.

    You should rethink your opinion.

    H =)

Viewing 3 replies - 1 through 3 (of 3 total)