Re: blob and network packet size
- From: "Matt Neerincx [MS]" <mattn@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 21 Aug 2005 21:55:20 -0700
In general the network packet size setting should be left alone, it is not
going to give you much one way or another in terms of performance.
The main reason I say this is everything has to go across TCP-IP, which has
a limit of ~1430 bytes per packet. So the TDS packet size is not the
limiting factor. Everything is squeezed down into ~1430 byte TCP packet in
the end.
Another problem with cranking it up is that it causes SQL Server to also
chew up more memory holding larger packets, reducing scalability. So 4K
default is good. Network packet size > 8000 bytes should be avoided for
server scalability reasons, this causes SQL to allocate packets out of
mem2leave area instead of normal buffer pool.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"dp" <dp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1DAAA61D-5512-45A1-83F4-BAD4EF1CDDB7@xxxxxxxxxxxxxxxx
> 1) For performance of BLOB only data that will have at least 100 KB per
> BLOB,
> what is the best network packet size setting? The resource kit indicates
> that
> it is 8080. Is that correct, or is it a typo that should say 8192?
>
> 2) Does the client connection have to match the network packet size
> setting
> for it to be used?
>
>
>
>
.
- References:
- blob and network packet size
- From: dp
- blob and network packet size
- Prev by Date: Re: Please Help! CryptAPI Error - Connection issue.
- Next by Date: Re: SQL or ISA firewall problem
- Previous by thread: blob and network packet size
- Next by thread: Re: Cannot connect to MSDE on SBS 2003
- Index(es):
Relevant Pages
|
