|
|
Posted by Bob Barrows [MVP] on 09/28/07 12:52
bzh_29 wrote:
>> If you run your application on a WAN, you need to be more considerate
>> with your design.
> Excatly. We're working since a long time to avoid any unneccessary
> table or column.
>
>> Make sure you don't return unneeded columns in your result set (no
>> SELECT *!). Also make sure that you don't have a lot of extra
>> network roundtrips. If you need to find data for ten orders, run one
>> query not ten.
>
> Request are build to return only needed columns and we use a package
> analyser to see what's going on on network to optimize network
> traffic.
>
> It's with this analyser I see that when I send one byte in fact I send
> two ... I understand the reason you explain before but as my apps will
> never feet for japanese ou chinese needs, I'm a little sad to not be
> able to avoir such things ...
>
> Need to continue optimize every char I send ...
Ummm ... there is obviously something else going on here. You're trying to
tell us that sending two bites instead of one results in 84X (5 sec to 7
min) slower performance??? I don't think so. At worst, there would be a 2X
drop in performance, and even that is not likely (please, someone step in
and correct me if I'm wrong). My guess is an overloaded network or perhaps a
defective router or switch somewhere.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
Navigation:
[Reply to this message]
|