comments on performance
Russ Ross russ@russross.com
Sun, 29 May 2011 09:30:57 -0600
1 files changed,
8 insertions(+),
2 deletions(-)
jump to
M
README.md
→
README.md
@@ -52,8 +52,14 @@ than upskirt (Go's bounds-checking uncovered a few off-by-one
errors that were present in the C code). * Good performance. I have not done rigorous benchmarking, but - informal testing suggests it is pretty fast. Probably not as - fast as upskirt, but probably faster than most others. + informal testing suggests it is around 8x slower than upskirt. + This is still an ugly, direct translation from the C code, so + the difference is unlikely to be related to differences in + coding style. There is a lot of bounds checking that is + duplicated (by user code for the application and again by code + the compiler generates) and there is some additional memory + management overhead, since I allocate and garbage collect + buffers instead of explicitly managing them as upskirt does. * Minimal dependencies. blackfriday only depends on standard library packages in Go. The source code is pretty