|Sent on:||Tuesday, October 23, 2012 2:57 PM|
Examine your collection usage and collection types.
Look for obvious non-linear scaling usage such as insertion sorts, sequential queries, suboptimal hashes, list traversals etc. Study the Big-O notation rules....
Good morning,I'm working on a rather high trafficked ecommerce platform at the moment where I seem to having some performance issues.I've hooked visualJVM up to the application to find that one particular method is taking over 40 seconds to complete when load is high. Looking at the method, I see it's a 185 line copy and paste job from a legacy codebase that has some rather verbose conditionals and lots of interactions with Collections.I know I haven't given enough information for anyone to really help me but I'm curious as to how you would generally go about dealing with a 185 line, synchronised java method that was lifted out of a legacy codebase. Where am I supposed to begin when refactoring this mess?Craig
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Craig Silk ([address removed]) from LJC - London Java Community.
To learn more about Craig Silk, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]