speedup Orbeon

Hi all,

I still have performance issues in Orbeon 3.8 with large forms.

Just retrieving the page, tested with a wget command to make sure the
browser is not a bottleneck, takes around 20 seconds and sometimes up to
more then a minute.
Filling in the first field, and tabbing to the next field triggers a
validation on the first field (showing the 'loading' in the top)
this validation takes anywhere between 5 and 10 seconds.
As you can imagine, those response times are not really user friendly, I
attached one of the big forms we have build.

We are running on Tomcat 6.0.18, Orbeon 3.8 PE (also tried this form on
Orbeon 3.9 PE, almost no difference in performance)

Startup settings:
-XX:MaxPermSize=1024m 
-Xmx1024

Does anybody has suggestions how we can speedup things, maybe we should
buildup our forms differently?
Please dont just give the answer migrated to 3.9 because thats not the
solution, as I tested the form also in Orbeon 3.9 and no big differences
were noticable. Unless you have some metrics prooving that Orbeon 3.9 with
the new ehcache can speed things up?

regards Ramon
http://orbeon-forms-ops-users.24843.n4.nabble.com/file/n3903972/example_big_form.xml
example_big_form.xml 

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/speedup-Orbeon-tp3720486p3903972.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.

Ramon,

>>> do you mean the $variables here? or constructions like .. and .

It's for every XPath expression lookup (compiled expressions are cached).

> * The good news is that I think this code can be greatly improved.
>>> do you mean I can improve the xhtml or that Orbeon can improve the
>>> javacode?

Here I mean in the Java code. I am, maybe naively, hoping to have a
look at this this week.

>>> if you mean the xhtml could you give me some directions where to start?
>
> Finally, since the form only shows a pretty small amount of data on screen
> at a given time, I am thinking that more optimizations are possible, whether
> at the XForms engine level or by working on the form itself.
>>> we already thought that we might had to look into splitting up the page,
>>> but saying that is more easy then actually building it. Do you an
>>> idea/example how to split these pages up.

Not instantly. I haven't analyzed your form as that might take a
while. Do you use relevance to hide/show the different tabs?

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

---

If you reply to this email, your message will be added to the discussion below:

http://orbeon-forms-ops-users.24843.n4.nabble.com/speedup-Orbeon-tp3720486p3917534.html

To unsubscribe from speedup Orbeon, click here.

Ramon,

Glad this helped!

Note that this is typically related to Form Builder-generated forms.
Form Builder places a name attribute on every bind. If you have
hundreds or thousands of those, you can hit performance issues. We
have a pretty good idea of why this is happening, and hope to resolve
this soon.

-Erik

On Tue, Nov 15, 2011 at 9:53 PM, Ramon de Beijer
<[hidden email]> wrote:

> if other people also have this problem, thanks to a tip from Erik we were
> able to speedup the performance with a big step forward.
>
> The trick is to be careful with giving every bind a name, in our case we
> only give the binds that are referenced by $bindname a name property (for
> example in relevance or calculate attributes of other binds)
> this speeds up the loading of the form and the loading action after tabbing
> out of a control dramatically.
>
> the snippet from Erik's mail:
> Now there might be a workaround that might help: in your form, on
> <xforms:bind> elements, you will notice all the @name attributes.
> Those expose bind as variables. It is likely that few or none of those
> are actually needed by your form. So you could try to remove all those
> bind/@name attributes and see if your form runs faster. That would be
> something to try.
>
>
> tnx again Erik
>
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/speedup-Orbeon-tp3720486p4075424.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

---

If you reply to this email, your message will be added to the discussion below:

http://orbeon-forms-ops-users.24843.n4.nabble.com/speedup-Orbeon-tp3720486p4075439.html

To unsubscribe from speedup Orbeon, click here.
NAML