That would probably be a handy feature Drew.
I tell my developers to develop with initially with all requests set to
5s, this enables them to catch issues at an early stage and work towards
making them faster.
... certainly when debugging and stepping through it's necessary to have
long timeouts.
-- Anthony.
On 28/08/13 21:34, Drew Wills wrote:
Perhaps one thing we need is a manageable way to configure different
timeout values for production and everything else.
drew
On 08/28/2013 01:26 PM, Anthony Colebourne wrote:
Hi James,
In my experience I would recommend extreme caution when raising portlet
timeouts.
Under heavy load, it is very easy to use up all the portlet rendering
threads.
Just this morning I accidentally mis-configured a portlet who's time out
is 10000 and brought down our servers. We're pretty strict about timeout
values and almost all of our portlets use the 5s default.
We in many cases use ajax to load content from long-running processes.
I'm some of these cases I have reluctantly raised to timeout of the
resource requests only.
I would like to see documented the relationship between rendering
threads and timeout values, also how this relates to tomcat threads and
apache threads where applicable. (I guess db connection pools are also
impacted, both portal and portlet?).
Some guidance on how to choose sensible thread/timeout values based on
averages such as portlets per page / server resources would be useful.
I'm happy to provide information and statistics from our production
cluster if it helps?
-- Anthony.
On 28/08/13 20:08, James Wennmacher wrote:
I propose we change the portal's default render timeout from 5000ms to
20000ms. There are portlets that tend to take long time (such as email
preview) or custom portlets connecting to back end systems where 5000ms
is sometimes too short a time.
I think the user experience in general would be better to have a longer
default so:
- The portal doesn't display an unpleasant message to the user for
longer-running scenarios
- The portal is more tolerant of operational issues such as uPortal or
dependent systems running a bit slow
- Longer-running processes should typically use ajax requests to obtain
the data for a better user experience, so the urgent user response is
less important in these situations since the entire UI is not impacted
This would affect new portlets that are created via the UI (or imported
without a timeout value I believe) but not existing portlet instances.
Thoughts?
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
