[julien1]

removing JTA will not give you an extra performance boost as during the commit phase, every datasource (actually only the PortalDS) will say nothing has been changed and the TM will optmize. So the overhead is very minimal.

Yesterday I improved the way that portal objects and instances are looked up. They are lookup up by natural id, which has a significant cost in hibernate (and it should not). I have added a cache of natural-id to PK which eliminates the hibernate Query object in my profiler hotspot. It's in 2.4.1 branch and 2.6 trunk.

My advice : you should consider to implement PortalObjectContainer and InstanceContainer as read-only in-memory store (well just maps of maps). That will give a significant performance boost at the cost of no flexibility (since it's immutable.

"walbar" wrote:
Anyway we don't need JTA in production since most of our portlets' logic would be read-only. We would use JTA during Staging, and in that phase we are not interested in performance yet.

So, I'm still interested in knowing where I could remove JTA transactions. Would you help me?

Thanks a lot,

Waldemar