long view renders.

[Brenda Wallace]

I'm seeing some views on an Alaveteli taking a really long time to render. Result is some requests that take 40 or 60 or more seconds to complete through rails. These clog up all the passenger processes and everything else queues up behind them.

Is there a way to tell rails/alaveteli middleware (is it rack?) to give up if it's taking longer than X? I'd rather fail those few requests (and then diagnose them) than our current situation where all passenger processes are busy and everything queued

[Gareth Rees]

Looks like there is in passenger, but it's a paid-for option: https://www.phusionpassenger.com/docs/references/config_reference/apache/#passengermaxrequesttime

You could look at whether there's something to do at the web server level (e.g. https://httpd.apache.org/docs/2.4/mod/mod_reqtimeout.html) but that might not actually kill the rails process as you suggest.

There might well be something on the rails/rack side that could do this, but nothing immediately comes to mind so would need a bit of research. Do let us know if anything useful arises, and if you make any performance improvements to views that we can pull back in to Alaveteli core.

Best,

Gareth

[Brenda Wallace]

Reporting back. In August, I found the parts of the views that were taking a very long time, and commented them out.  you can see what we had to do here:

https://github.com/openaustralia/righttoknow/pull/906/files

We were still on Alaveteli 0.38 back then, and we've upgraded Australia to 0.40 in early September, and are hoping to leapfrog to 0.43 soon. (We have had to find ways to deploy the 0.41 and 0.42 temp rake tasks to do this)