e a
> CSV file and create metrics and SLA over those metrics, plot graphs and so
> on. Pretty nice tool!!!
>
> I'm wondering if we could start to test something and maybe show it at
> AsiaBSDCon and BSDCon(Canada) next year? What do you think?
> What I need right now would be a list of tests that we want to perform as
> well as what parameters we would like to take as metrics to compare.
>
> Best Regards,
>
>
Would this work for testing other things, like SSH performance? I am
looking at doing some SSH + HPN tests to prove that it is worth keeping.
--
Allan Jude
signature.asc
Description: OpenPGP digital signature
ers are highly appreciated, I can't believe that there is such
> a blatant difference in network performance compared to Linux.
>
> Regards,
> Wolfgang
>
I wonder if this might be NUMA related. Specifically, it might help to
make sure that the 8 CPU cores that the NIC queues are pinned to, are on
the same CPU that is backing the PCI-E slot that the NIC is in.
--
Allan Jude
signature.asc
Description: OpenPGP digital signature
On 2016-02-03 16:34, Adrian Chadd wrote:
> hi,
>
> can you share your testing program source?
>
>
> -a
>
I have a Dual E5-2630 v3 (2x8x 2.40ghz (+HT)) with the Intel X540-AT2
that I can try to replicate this one to help debug it.
--
Allan Jude
signature.asc
Descrip
ation.
Concerning pcb hash table size I only found net.inet.sctp.pcbhashsize and that
had no influence. Not sure whether sctp plays a role at all in my problem.
Regards,
Wolfgang Meyer
I think the one you are looking for is: net.inet.tcp.tcbhashsize
See if doubling that makes a difference.
--
eebsd-performance
> To unsubscribe, send any mail to
> "freebsd-performance-unsubscr...@freebsd.org"
You might try pktgen, the netmap tool for generating packets, rather
than iperf, as your source of traffic.
Olivier Cochard-Labbé has a series of benchmarks on github in his
e default (2000 mhz) to 2001
mhz, which will enable turbo boost (this specific CPU bursts to 3700
mhz), so this will likely make a very large difference in your benchmarks.
To get more consistent results, you may actually want to disable
turboboost in the bios, and rerun the benchmarks on ALL o
