Thanks for providing build scripts and sharing results. Just a quick heads-up from me: I have implemented a simple sender/receiver pair using C sockets as well as CAF brokers (attached, but works only with the current actor-system topic branch). Both sending and receiving are slower with CAF (as expected), although the performance is slightly better when using the ASIO backend [1]. I'm still investigating and hopefully come back to you guys later this week.
Dominik
[1] e.g. ./caf_impl --caf#middleman.network-backend=asio -s
> On Feb 25, 2016, at 17:19, Matthias Vallentin <vallen...@icir.org> wrote:
>
> For better reproducibility, here's the Makefile that I used to drive the
> experiments:
>
> CC = cc
> CXX = c++
> FLAGS = -O3 -g -std=c++11 -stdlib=libc++
> LIBS = -lcaf_core -lcaf_io -ltcmalloc -lprofiler
>
> caf-client: caf-client.cpp
> $(CXX) $(FLAGS) $< -o $@ $(LIBS)
>
> caf-server: caf-server.cpp
> $(CXX) $(FLAGS) $< -o $@ $(LIBS)
>
> bench-caf-client:
> CPUPROFILE=caf-client.prof ./caf-client 1000
>
> bench-caf-server:
> CPUPROFILE=caf-server.prof ./caf-server 10
>
> bench-caf-pprof: caf-client.prof caf-server.prof
> pprof --pdf caf-client caf-client.prof > caf-client.pdf
> pprof --pdf caf-server caf-server.prof > caf-server.pdf
>
> On my FreeBSD box, I had to add /usr/local/include to -I and -L, because
> I installed CAF and gperftools via ports. Since it's a headless machine
> without ps2pdf, we need extra level of indirection:
>
> (1) pprof --raw caf-client caf-client.prof > caf-client.raw
> (2) copy raw profile to desktop
> (3) pprof --pdf caf-client.raw > caf-client.pdf
>
> Hope this helps,
>
> Matthias
caf_impl.cpp
Description: Binary data
Makefile
Description: Binary data
native_impl.cpp
Description: Binary data
_______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
