tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H de Paula Figueiredo" <thiag...@gmail.com>
Subject Re: Decrease number of ThreadLocal.get calls
Date Fri, 01 Aug 2014 21:19:48 GMT
On Fri, 01 Aug 2014 17:03:20 -0300, Howard Lewis Ship <hlship@gmail.com>  

> This issue:
> https://issues.apache.org/jira/browse/TAP5-2333
> has a patch that improves performance by a noticable amount BUT means  
> that we lose the "operations trace" (at least, in production).
> I'm pretty sure I want to keep the operation trace, even at the cost of
> performance.

What's this noticeable amount? A ballpark figure would be nice.

Could we control this by a configuration symbol and have the default being  
working as it does now? This way, we can choose what trade-off we want.

Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message