Whatever it be, we had a bad time with TreeCacheAOP.From our profiling, just a get() that was doing some doing a lock ( some intent.lock package) was hogging up cpu time...
Do u have any clue why this would take time..
We are using 1.2.x version of TreeCacheAOP..
We do have puts, and remove operations on the cache...
By they way, we are using the AOPProxyCollections for replicating our collections like HashMaps and Lists.
Could there be a botteneck in the proxies?
OK. We have had optimization for Collection class in 1.3 and then more in 1.4. Can you try out the latest one in 1.4beta. We should release it in 2-3 weeks.