Dick Zetterberg wrote:
Not creating a new HashMap all the time sounds like a good idea. I'd prefer to have it created lazily though so that it is not created when it is not needed (when you do not have any parameters for example).
Concerning the StringBuffer re-use: Did you measure the performance
Title: RE: [OS-webwork] URLBean performance issues
Hi, this may be related but I don't know the code you're talking about and any profiling you may have done but I'm gonna throw this into the mix anyway.
Guessing URLEncoder is used to generate URLs in your app. If you wan
Title: RE: [OS-webwork] URLBean performance issues
Hi, this may be related but I don't know the code you're talking about and any profiling you may have done but I'm gonna throw this into the mix anyway.
Guessing URLEncoder is used to generate URLs in your app. If you wan
From: "boxed" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 07, 2003 9:54 AM
Subject: [OS-webwork] URLBean performance issues
> I have a pretty large velocity page that needs to generate a lot of
> urls, and I noticed that the roughly 4000 urls generat
Can you please create a Jira issue and attach these there?
> -Original Message-
> From: boxed [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 07, 2003 3:55 AM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] URLBean performance issues
>
>
> I have a pretty
I have a pretty large velocity page that needs to generate a lot of
urls, and I noticed that the roughly 4000 urls generated with the
URLBean class took about two seconds to generate. I took a look at the
code and saw that it creates and throws away a StringBuffer AND a
HashMap every single ite
