I'm sure others have addressed most points, but I thought I will mention something that hopefully is obvious (apologies if so): make sure that whatever changes you make solely to improve performance are actually tested to improve performance. I mention this because many of the things you list often yield any observable improvements (unless used in some significant tight loops, perhaps), because while they may relatively speed things up, it may be irrelevant because bottlenecks are elsewhere.
-+ Tatu +- ----- Original Message ---- From: Pascal S. de Kloe <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, October 26, 2007 5:46:54 AM Subject: Performance A client of mine is having some serious performance problems with the HTTP client and requested to improve things. Do you accept patches like the attached one? * Lazy initialization * Use indexed ArrayList methods * Removes the need for CookieIdentityComparator --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
