3 ms·
Ah thanks! So nothing to do with GC or poor IO but a poorly selected operation to do in a benchmark.
by hartror 15y ago
Ah thanks! So nothing to do with GC or poor IO but a poorly selected operation to do in a benchmark.
- drivebyacct2 15y agoAs it seems like is always the case in these fairly naive benchmarks. (Not specifically about Go here, it seems like people often cite python when they're really using some optimized C code).
- berntb 15y ago>>poorly selected operation to do in a benchmark. Considering the history of benchmarks, it is quite likely the opposite: The library was selected very carefully, to argue a "point". :-(