LiveCode Forums.

Hello All,

1. Is there a maximum execution time pre-configured in On-Rev for iRev scripts?

2. Is there a way to set the maximum execution time of an iRev script? Similar perhaps to the way it is done in PHP [eg. set_time_limit(0); ]

Any assistance, greatly appreciated.

Kind regards, Andrew

You should probably post this question on the dedicated On-Rev forum, rather than this generic forum.

Jan Schenkel.

Jan,

Just won a Coke for betting a colleague, that the first reply to this post would inform me that it is posted in the wrong place. A little unfair, but thanks (sincerely).

You are absolutely right, I apologise, and I have duplicated this post @ http://forums.on-rev.com/viewtopic.php?f=3&t=394.

I do however find the on-rev forum akin to a 'sleepy country town' compared with the 'big city' of these forums, and I equally find it more than a little weird that the On-Rev forum should not naturally fall within the structure of the main RunRev forum. It might create greater awareness of On-Rev for newbies stumbling upon Rev for the first time.

I am sure the Enterprise Users will one day experience some burnout from being compelled to watch two forums (runrev, on-rev), and two lists (use and for Enterprise customers improve). If Rev is say one of five tools you use, it can be time consuming. For the more experienced such as yourself, my guess is that there isn't much time in your world to keep tabs on the on-rev forum.

Perhaps I have it all wrong. Jan, thanks for posting.

Kind regards, Andrew

Hi Andrew,

iRev is set to allow 30 seconds execution time and 64mb memory. At the moment this can't be configured.

The execution is measured using CPU time, so in real-time its likely to be quite a bit longer than 30 seconds, depending on how CPU-intensive your code is.

I think the default apache timeOut is around 300 seconds, so its possible that apache may timeOut before iRev does.

Hope this is some help

Regards
Oliver

Oliver referred only to "iRev" without specifying whether he meant on-rev.com or the RevServer engine, which has contributed to some misunderstandings related to his post. Since Oliver is no longer with RunRev, let me briefly clarify this in his absence:

Subsequent discussion on the use-rev list has confirmed that these limits only apply to the shared-hosting service at on-rev.com, as are common on such services and usually apply to all processes including CGIs, PHP, MySQL, and anything else running on the account.

30 seconds is a very long time for a server process to be running, and 64 MBs is a tremendous amount of memory to use on a shared system, so as with most shared-hosting services one can expect relatively few users to be affected by these limits.

For those who need to run more resource-intensive processes, the RevServer engine can be used on any dedicated host without such limits. Benchmarks show the performance of the RevServer engine to be on par with PHP in similar configurations, which is to be expected given the long history of similarly good performance from the older Rev CGI engine so many have been using reliably for more than a decade.

Andre Garzia, one of the more experienced server admins in the Rev community, has put together some notes on using server processes effectively which should alleviate the implications of those types of common limits even on many shared-hosting configurations:

"Spreading the load or why wise developers use asynchronous workflows"
http://andregarzia.com/async.irev