3 ms·
"Guice may not show up on any profiler as problem - but if you slow down object creation by a factor of 40x, something you may do thousands of times per second
by al2o3cr 12y ago
"Guice may not show up on any profiler as problem - but if you slow down object creation by a factor of 40x, something you may do thousands of times per second for the life of your program, you are degrading performance across the board."
If your profiler doesn't point right at the thing that you're doing 40x slower thousands of times, either your profiler is BROKEN or that isn't actually a bottleneck.
- thrownaway2424 12y agoIf you have ten thousand different kinds of objects then the creation of instances of any given class will not rise to the top of the profile.
- LnxPrgr3 12y agoWhen I care about performance over most anything else, I take this guy's approach: https://www.youtube.com/watch?v=Kdwwvps4J9A https://www.youtube.com/watch?v=Kdwwvps4J9A It's not appropriate for every project, but if maximizing performance is your goal, you should be tracking performance constantly as you work, not as an afterthought late in the project. Late profiling leaves too much room for a thousand small inefficiencies to add up, and it adds too much time between making a decision and understanding its impact on performance.