6 ms·
50x isn't reasonable, it's a cache disaster. Any perf win from avoiding JIT gets eaten alive.
by JoheyDev888 4mo ago
50x isn't reasonable, it's a cache disaster. Any perf win from avoiding JIT gets eaten alive.
- dzaima 4mo agoOnly if it is all actually used at runtime; and presumably the vast majority of possible decoding starting points won't be.
- po1nt 4mo agoI wouldn't jump to conclusions. Instructions aren't so big anyways and they are optimized JIT by CPU.
- wmf 4mo agoThis is a great case for link-time code reordering. You can put all the hot code together so the unused code will never be loaded.