05-24-2010 01:59 PM
CSS 11501
8.10.2.05
We have a client with a basic layer-4 content rule, no advanced balance/sticky sessions, leastconn. Using Firebug for Firefox, I've tested a website containing several and noticed that there is a noticeable delay (roughly an added 1-2 seconds) specifically in the client receiving some of the .SWF content (about 6 files at around 100KB each) from the VIP address, but not when called directly from any one of the the servers directly. From the servers directly, all .SWF content is downloaded and received by the firefox client in around 300ms each. When accessing the VIP however, they take anywhere between 300ms and 2 full seconds, the average usually landing in the middle of that range.
Is this the expected performance of the CSS?
service vm1
ip address <server.address>
keepalive type http
keepalive uri "/check.txt"
active.
service vm2
ip address <server.address>
keepalive type http
keepalive uri "/check.txt"
active
service vm3
ip address <server.address>
keepalive type http
keepalive uri "/check.txt"
active
service vm4
ip address <server.address>
keepalive type http
keepalive uri "/check.txt"
active
content customer_vip1
vip address <vip.address>
no persistent
balance leastconn
add service vm1
add service vm2
add service vm3
add service vm4
protocol tcp
port 80
active
Solved! Go to Solution.
05-25-2010 01:36 AM
The content rule being L4, once the loadbalancing decision is made with the SYN packet, the connection is simply switched like any normal switch device. So, the CSS does not even know this HTTP or that the file is .swf.
In other words, it should work the same no matter what the type of traffic and therefore a 2sec delay is not normal.
Did you capture a sniffer trace on client and server when going through the CSS to see what is happening ?
Gilles.
05-25-2010 01:36 AM
The content rule being L4, once the loadbalancing decision is made with the SYN packet, the connection is simply switched like any normal switch device. So, the CSS does not even know this HTTP or that the file is .swf.
In other words, it should work the same no matter what the type of traffic and therefore a 2sec delay is not normal.
Did you capture a sniffer trace on client and server when going through the CSS to see what is happening ?
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide