We are running uPortal 4.0.5 in pilot at the moment here at UWE and we have been experiencing serious performance issues, as described by my colleague Sarah Sloan in the following post : http://jasig.275507.n4.nabble.com/uPortal-4-performance-compared-to-uPortal-2-td4654203.html
After much investigation we believe the problem lies with transaction handling in the following classes: JpaPortletDefinitionDao and JpaPortletEntityDao. I found that the ‘@Transactional(readOnly=true)’ annotation was causing (what I believe to be) unnecessary transactions to be used around methods which only read from the database. The following information helped me understand the correct use of this annotation: http://www.ibm.com/developerworks/java/library/j-ts1/index.html (*Listing 8*) Removing these annotations from uP4 results in page renders running between 100% and 200% faster, at least according to our benchmarks, and on our Solaris servers. The removal of these annotations appears safe to me, any advice/comments from the community gratefully received. Sean Reed UWE UK -- 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
