32. LVS: Performance and Kernel Tuning
We are now (2006) in an era where the CPU is no longer rate determining in an LVS director. Ratz 20 Feb 2006 The processor never is an issue regarding LVS unless your NIC is so badly designed that the CPU would need to take over the packet processing ;) (a non-LVS article on Configuring large scale unix clusters by Dan Kegel.) The article performance data for a single realserver LVS, shows how to
8. LVS: LVS-Tun
LVS-Tun is an LVS original. It is based on LVS-DR. The LVS code encapsulates the original packet (CIP->VIP) inside an ipip packet of DIP->RIP, which is then put into the OUTPUT chain, where it is routed to the realserver. (There is no tunl0 device on the director; ip_vs() does its own encapsulation and doesn't use the standard kernel ipip code. This possibly is the reason why PMTU on the director
28. LVS: Persistent Connection (Persistence, Affinity in cisco-speak)
"persistent connection" a term used for clients connecting to webservers and databases. For Apache this is called a "keepalive" and is set in httpd.conf and is described in persistent_http. "persistent connection" used in LVS. LVS persistence is closer to the concept of "affinity" as used by cisco The two types of persistence are quite different. Unfortunately, both features are persistent and can
4. LVS: Ipvsadm and Schedulers
ipvsadm is the user code interface to LVS. The scheduler is the part of the ipvs kernel code which decides which realserver will get the next new connection. There are patches for ipvsadm machine readable error codes for ipvsadmstateless entry of ipvsadm commands Mar 2004. There appears to have been introduced a bug in the wrr code. Presumably this will be fixed sometime in the main code, and pres
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
