Posted by TheSQLGuru on 09/02/07 14:01

IMHO, with all other things being equal designing for fewer round trips to
the server usually equals better scalability and usually better performance
as well. Note that these two things are NOT synonymous and can often be at
odds with each other - especially on the high end of each spectrum.

Performance analysis and tuning is a VERY complex and complicated process
when you are really trying to optimize an entire application. There are
HUGE numbers of moving parts and parameters within each subsystem. Usually,
however, an expert at this realm of problem solving can use knowledge,
experience and his/her toolset to quickly isolate the most egregious
offenders and point the dev/hardware team to the sections that are either
"low-hanging fruit" or will give the biggest bang for the buck.


--
TheSQLGuru
President
Indicium Resources, Inc.

"Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom> wrote in message
news:%23YrbnvM7HHA.3900@TK2MSFTNGP02.phx.gbl...
>> In addition to agreement with others statements about refactoring the
>> application to reduce network traffic
>
> Sure. Dont disagree. I could arrange that I get 5 records back from a SP
> query instead of 1 record back per query.
> And it may well be that 5 records fit in a network packet.
> That is 1 round-trip rather than 5 round-trips.
> But it could be that I squeeze 10 records or 20 records etc.
> How do we determine this without endlessly going round some design-cycle
> trying magic numbers which immediately alter if the fields in the query
> alters?
>
> Thanks
>
> Stephen Howe
>

[Back to original message]