What could help to achieve better performance is variety of stress tests
which could be run as a part of the Seam build.
They would also have helped to understand how ongoing changes to Seam
impact the overall performance.
Each stress test should address a specific aspect of JSF application to be more
useful in troubleshooting and profiling.
Here are some ideas about use cases for stress testing
1. Rendering large table - measure response time (stress testing of EL, etc)
large number of columns and rows
2. Submitting big form (stress testing of validation and apply request values
phase)
3. Some repeatable evaluations of EL expression
4. Stress test case for injection/outjection
Backing bean with many In/Out annotations
5. Stress test case for annotation reading via Seam APIs
6. Stress testing of AJAX responses when using AJAX4JSF,
(by trying to rerender large area by Ajax)
7. Stress testing of EntityConverter
trying to render many dropdowns
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099629#4099629
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099629
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
