add benchmark results to docs

[gucki]

You state your library is high performace, but It'd be great if the docs would contain some performance numbers/ benchmarks compared to net/rpc. Especially for different workloads (small requests, large requests with byte slices, ...).

[valyala]

I'll definitely add real-life benchmark results comparing gorpc to net/rpc (and, probably, other popular rpc implementations) into README.md.

Currently bench_test.go contains benchmarks, which can be used for performance comparisons with certain grain of salt. Here are results from my machine:

    $ go test -run=None -bench=rpc
    PASS
    BenchmarkNetrpcInt-4           50000         29676 ns/op
    BenchmarkNetrpcByteSlice-4     50000         30501 ns/op
    BenchmarkNetrpcStruct-4        20000         75986 ns/op
    BenchmarkGorpcInt-4           100000         20267 ns/op
    BenchmarkGorpcByteSlice-4      50000         21694 ns/op
    BenchmarkGorpcStruct-4         20000         62887 ns/op

These results may be far from real life, since both server and client are running on the same machine during benchmarks. In the real world client and server are usually located on distinct physical machines connected over the network. Gorpc should work faster in the real world, since it:

• minimizes the number of send()/recv() syscalls under high load (which, in turn, should minimize the number of network packets required for rpc).
• minimizes the amount of data floating over the network between client and server.

[renanbastos93]

Maybe, we can put on benchmark to compare with gRPC