In order to use newer security features we are looking to move to building
and deploying 2.7d before an official package is available from Ubuntu.

However, what I find when I build it myself, and put it under stress in our
testing environment is that we get significantly worst performance as
compared to "official" 2.5 package and we see the the following error in
our apache log repeated again and again:

message repeated 13 times: [ HTTP accept: Too many open files]

I am hoping the pour performance and file issue has something to do with
the way that I am building pound and/or the level of debug that is turned
on.

I asked a general question on Friday, not giving as much information, but
had hoped that someone would reply with the most performant way in which to
compile 2.7d, but since no one answered I am asking again with more
information.

Thanks in advanced

Anthony Tarlano

Reply via email to