> Did you by any chance carry out benchmarks comparing
> performance before and after your changes?
In this case no, although I've benchmarked these kinds of changes
before. For small collections the changes are minimal but can add up
quickly if the collections are used frequently. Large collections will
see more benefit.
I've seen a number of cases where I've been able to shave seconds off
execution time by making small changes like these to common
"infrastructure" type components even when the individual collection
sizes were relatively small.
--
Mike Bowler
Principal, Gargoyle Software Inc.
Voice: (416) 822-0973 | Email : [EMAIL PROTECTED]
Fax : (416) 822-0975 | Website: http://www.GargoyleSoftware.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
- [PATCH][LANG] Initial collection sizes in Enum.java Mike Bowler
- RE: [PATCH][LANG] Initial collection sizes in Enum.java Shapira, Yoav
- Mike Bowler
