I’m thinking of running Perlbal for load balancing, and I see that it can also act as a Web server for static content. So I’m wondering: for static content, is it better to run Perlbal proxying to an http server (say lighttpd), or to have Perlbal serve the static content itself?

In production my static content will be on its own separate subdomain (static.something.com). Am I better off running lighttpd to serve this content (just lighttpd, no Perlbal in front of it) or will Perlbal (just Perlbal, no lighttpd behind it) do the job? Anybody know of any good Perlbal vs. Lighttpd benchmarks for static content serving?