Tux's primary aim is static content, but it will handover the
connection to a _user space_ webserver if it's a dynamic page. I have
absolutely no idea how many (Open)ACS sites are streaming a lot of
static content like images, music and movies. Those sites may benefit
greatly. But I do think Tux is something for the OpenNSD (how is that
comming along?) crew to look at, at first.
If I understand correctly from the kernel-traffic-digest (kt.zork.net)
Tux does most of it's magic by mapping the disk-I/O buffers to the
same location as the Network-I/O buffers, saving atleast one
buffer-to-buffer copy on each page hit. If you read the discussions on
Tux (and SPECWeb) you will find people who consider Tux a gimmick to
people who never want to live without it again.
I can not backup my hypothesis with actual data, but my guess is that
almost any machine capable of doing web/db has more internal I/O
bandwidth than is ever going to be consumed by network I/O.
