On Tue, 2013-05-21 at 16:15 +0300, Alex Rosenbaum wrote: > On 5/21/2013 3:29 PM, Eliezer Tamir wrote: > > What benchmarks are you using to test poll/select/epoll? > for epoll/select latency tests we are using sockperf as performance > latency tool: https://code.google.com/p/sockperf/ > It is a client-server based tool and it supported ping-pong, throughput, > and under-load test type. > For epoll, you will need to define a 'feedfile' ("-f filepathname") > which has a list of TCP and/or UDP socket and defined your IO mux type > ("-F epoll").
I totally agree, most modern applications use poll/select/epoll, and a fair amount of sockets per task, sendfile()/vmsplice()/... and netperf is not using same paths. Thanks Alex ! ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
