[表示 : 全て 最新50 1-99 101- 201- 301- 401- 501- 601- 701- 801- 901- 2chのread.cgiへ]
Update time : 10/23 11:10 / Filesize : 237 KB / Number-of Response : 923
[このスレッドの書き込みを削除する]
[+板 最近立ったスレ&熱いスレ一覧 : +板 最近立ったスレ/記者別一覧] [類似スレッド一覧]


↑キャッシュ検索、類似スレ動作を修正しました、ご迷惑をお掛けしました

【NTT西日本】 フレッツ・光プレミアム Part30



50 名前:名無しさんに接続中… mailto:sage [2008/10/09(木) 23:14:58 ID:gqu9U9FG]
A tip for RcvWin/TcpWindowSize tweakers

"I've most often seen [poor performance] with people running on Windows who 'tweak' their TCP send and receive buffers
to be very large in search of higher bandwidth. Buffered data is obsolete data and causes serious problems in the responsiveness
of the protocol to changes in the peer state. Since data and requests share the same TCP socket, buffering lots of data means that
your request for a block may have to wait 10's of seconds before it even gets transmitted, by which time the peer you are talking to
may have decided that you aren't interested in his data after all, or your own client may decide that the peer you are talking to is
snubbing you. Either of these is disastrous to download rates." - ( taken from the BitTorrent developer mailing list )

P2Pの場合RWinを大きくしすぎるとDL速度が低下するケースもあるらしい
BT以外のプロトコルではどうなのか知らないけど、参考までに






[ 続きを読む ] / [ 携帯版 ]

全部読む 次100 最新50 [ このスレをブックマーク! 携帯に送る ] 2chのread.cgiへ
[+板 最近立ったスレ&熱いスレ一覧 : +板 最近立ったスレ/記者別一覧]( ´∀`)<237KB

read.cgi ver5.27 [feat.BBS2 +1.6] / e.0.2 (02/09/03) / eucaly.net products.
担当:undef