https://bz.apache.org/bugzilla/show_bug.cgi?id=63235
--- Comment #7 from Phillip Webb <pw...@pivotal.io> --- > I don't see the benefit as there's a clear downside and the > complexity skyrockets. IMO you should focus on the String > optimization since it doesn't have these issues. I'll continue with the String optimizations as well, but they only help with memory and don't give any startup performance improvements. > On my desktop computer, I measured the "all charset" loading code using > System.nanoTime as taking 31105409ns, so that would be 31 ms. For me, saving 31 ms on each restart is a very worthwhile gain and something I'd love to be able to opt in to. I even think that when running on the server this kind of optimization is something I would find useful in many situations. For example, if I have many internal services that I know will all be hit with only UTF-8, why wouldn't I want to enable the option? I'd love to be able to find a solution that helps this use-case without adding too much complexity. From the comments on #57808 and #58859 it doesn't appear that I'm alone. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
