On Sun, Oct 04, 2015 at 12:09:26PM -0700, Daren Sefcik wrote: > On Sun, Oct 4, 2015 at 7:30 AM, joris dedieu <[email protected]> wrote: > > > Broadcom NICs : you should check man 4 bge and > > https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards > > > > While I had already looked at this early in my troubleshooting process I > totally screwed it up, I have bge cards and instead of changing the "bce" > configurations to "bge" I left them at bce. I changed them just now and was > able to easily achieve these numbers without a wink:
Interesting, so maybe in fact you're running on cards with an old horrible firmware like what I described in the previous e-mail. > *pid = *50054 (process #1, nbproc = 1) > *uptime = *0d 0h03m25s > *system limits:* memmax = unlimited; ulimit-n = 100047 > *maxsock = *100047; *maxconn = *50000; *maxpipes = *0 > current conns = 5562; current pipes = 0/0; conn rate = 64/sec > Running tasks: 1/5587; idle = 97 % > > I am going to load some real clients on to the system tomorrow when school > is back in session and see how that works, hopefully that is all I needed. > With Apache Bench I am getting good numbers on the stats page but my client > is still sluggish so I may have a bottleneck somewhere else now. Maybe your client is experiencing the same issue if it runs on similar hardware. Do not hesitate to do "pfctl -d" as suggested by someone (maybe Joris, I don't remember). It used to help a lot on openbsd in the past for similar reasons as conntrack on linux (session table full). At least you'll know. > I will report back with real world results, thanks for everyone's > suggestions so far, it is much appreciated. I do have some other questions > though I will post in a separate topic. Thanks for the report. Willy
