I doubt benchmarks be fair !!!

[Rustixir]

https://erlangforums.com/t/ring-benchmark-erlang-vs-go/684/12

in erlang community we did some benchkmarks around (raw golang) and ( erlang )
erlang was winner in message passing.
erlang internally used lock-free algorithm for registry and communication between mailbox.
but golang used mutex for channels !!! and in your framework heavily using mutex for synchronization !!!

how is ergo with overhead of framework can beats erlang ??!!!

[halturin]

We are moving the same way https://twitter.com/halturin/status/1634165290564034562

[halturin]

how is ergo with overhead of framework can beats erlang ??!!!

in terms of network messaging Erlang has poor performance due to the ETF encoder/decoder (lists/maps especially. as you may know, strings in Erlang are lists). Besides that, Ergo ETF has stack-less implementation

your framework heavily using mutex for synchronization

it depends on where it's used. In Ergo we use most of the time RWMutex, which is not the same as regular Mutex in terms of performance.

[halturin]

I move it to the Discussion. Hope you don't mind.

[halturin]

In case you wonder about MPSC implementation in Ergo https://github.com/ergo-services/ergo/blob/master/lib/mpsc.go

Here is the benchmark channel vs MPSC queue https://github.com/ergo-services/ergo/blob/master/lib/mpsc_test.go#L188

[Rustixir]

It looks good .
Thanks for your attention

[Rustixir]

But erlang can still beat ergo in many situations !!

For example :

When need in-memory transactional systems
Like RealTime bidding ( erlang have ets, actually is C code and don't make garbage )

[halturin]

But erlang can still beat ergo in many situations !!

not sure why you are arguing this way :)

When need in-memory transactional systems

there are so many different DBs implemented in Go :)

erlang have ets, actually is C code and don't make garbage

easy to check with golang's map (which is highly optimized), for example.

so, what is the point of your message?

[Rustixir]

Golang map is simple hashmap data structures

Erlang ets use judy array with highly optimize locking ( Judy arrays are highly optimized 256-ary radix tree )

Golang map make garbage and
have pressure on GC

But

Erlang ets is C based implemention
and don't make any garbage