3 ms·
The article seems to contradict itself, between "the Go implementation broke the speed record" and "Go makes the product too slow." Granted the cgo stuff and t
by daenney 10y ago
The article seems to contradict itself, between "the Go implementation broke the speed record" and "Go makes the product too slow."
Granted the cgo stuff and the memory usage would be something that one needs to deal with. Did you talk to go-nuts at all? They might've been able to offer some more insight into all of this, a better way to deal with the cgo related issue and perhaps even make some changes to handle these kinds of cases better.
- tvdw 10y agoHa, I see how it can sound like that :-) Yes, it broke the speed record: a multithreaded application outperformed the singlethreaded version. But I wasn't happy with the result. It consumed an order of magnitude more memory, and gc times were potentially harming users (not a widely researched subject, but gc times in low-latency mixnets can likely harm user anonymity). Oh, and it would occasionally crash with OOM errors.