[RevServer tips] Spreading the load or why wise developers use asynchronous workflows

Andre Garzia andre at andregarzia.com
Wed Aug 4 12:54:02 EDT 2010


Wayne,

you got it wrong, it is a per process limitation. The policies change from
shared hosting company to shared hosting company. At On-Rev means that a
single process can only use 30 secs of processing time, this is done
precisely to prevent a rogue process from using all the resources and thus
making the life of other users a mess. No one can hog the whole server for
30 seconds because, there is a CPU limit as well. It is not just time, the
limits are set so all users can reach the limit without affecting each
other. Thats the idea

Andre

On Wed, Aug 4, 2010 at 1:49 PM, wayne durden <wdurden at gmail.com> wrote:

> Hi,
>
> Just want to make sure I have the general understanding of the issues...
>  On
> a shared hosting setup where there is a process time limit such as 30
> seconds, would that mean that some other entity using the same server with
> an intensive process could latch essentially all of the processing for up
> to
> 30 seconds?  Is there a more finely granulated check that still swaps users
> in and out to a degree below a certain process priority claim?  And if the
> first assertion is the case, it wouldn't matter what tech one went with
> Rev,
> Ruby, PHP, etc. you could still get a wait time of almost 30 seconds before
> the server ended your sharer's processing and reached you, correct?
>
> Thanks,
>
> Wayne
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



-- 
http://www.andregarzia.com All We Do Is Code.



More information about the Use-livecode mailing list