In addition to Pat's comments, check out:
http://support.microsoft.com/?id=170964
If you want a test comparing concatenation -vs- just doing Response.Write(),
check out:
http://www.adopenstatic.com/experiments/stringconcatenation.asp
(note: you need to have Response Buffering on, otherwise using
Response.Write() a lot will be slow as well)
Cheers
Ken
"Pat [MSFT]" <patfilot.TakeThisOut@online.microsoft.com> wrote in message
news:ejeMNtJDEHA.2768@tk2msftngp13.phx.gbl...
: On the good news side, I don't see any evidence of a bug. What I do see
is
: a relatively busy server that appears to have some relatively expensive
code
: paths.
:
: Quite a few threads were busy doing string concatenation. It is important
: to note that in VB & VBScript every '&' and '+' requires the entry/exit of
6
: locks. Not only that, but strings become exponentially more expensive as
: they grow in size (after the size passes 100k or so). If a lot of threads
: are doing string concatenations, then the locks start to experience a
: 'convoy' (kind of like floating the valves in an engine). This is
: happening.
:
: What can be done?
:
: Start looking in the VB dll's and VBScript and identify extraneous '&' and
: '+'. A lot of times, these are added at a programmer's convenience:
:
: str = "My String"
: str = str + " is short"
:
: instead of having just one line. Also, you want to look for string
: manipulation in a loop. It's OK to do it, but you need to understand the
: expense and make sure that there are as few concats as possible.
:
: Pat
:
: >> Stay informed about: High cpu Utilization - IISState Log 
FAQ
Profile
Private Messages
Log in
