A common problem in shared hosting environments is where a user uses a malfunctioning script of some sort and it runs wild. Say this is a PHP script, so in this case it is one Apache thread by my understanding.
Am I correct in assuming that this one thread will only be able to abuse just one core, because the errant script is one thread, thus leaving the other cores of the server untouched?
What other ways and means are you currently practising to ensure resources aren't swallowed by an user-gone-wild in a shared environment?
Thanks,
Am I correct in assuming that this one thread will only be able to abuse just one core, because the errant script is one thread, thus leaving the other cores of the server untouched?
What other ways and means are you currently practising to ensure resources aren't swallowed by an user-gone-wild in a shared environment?
Thanks,