3 ms·
From the github README: > On the other hand, Fil-C is quite slow. It's ~10x slower than legacy C right now (ranging from 3x slower in the best case, xz decompr
by gmueckl 2y ago
From the github README:
> On the other hand, Fil-C is quite slow. It's ~10x slower than legacy C right now (ranging from 3x slower in the best case, xz decompress, to 20x in the worst case, CPython).
That performance loss is severe and makes the approaches totally uninteresting for a most serious use cases. Most applications written in C or C++ don't get to waste that many cycles.
- pizlonator 2y agoThose are old perf numbers. It’s sub-2x most of the time now, and I’m working on optimizations to make it even faster. Note that at the start of this year it was 200x slower. I land speed ups all the time but don’t always update the readme every time I land an optimization. Perf is the main focus of my work on Fil-C right now.
- Krutonium 2y agoMight I suggest having the CI benchmark it and then update the readme?
- pizlonator 2y agoIf I had the time to set that up then yeah. Right now I’m spending all my time actually implementing optimizations and measuring them locally. I did spend the time to give myself a good benchmark suite with a nice harness (I call it PizBench, it includes workloads from xzutils, simdutf, Python, OpenSSL, and others).