Wild and Mold linkers were benchmarked with conflicting results due to different hardware, filesystem configurations, and runtime settings. Wild performs better on tmpfs with fork enabled and pre-existing output files, while Mold's ext4+delete+no-fork configuration shows different performance characteristics. The authors are investigating performance differences and planning optimizations including fallocate and hugepages.
Wild and Mold linker benchmarks show performance differences due to varied testing configurations including filesystem type (tmpfs vs ext4), output file handling (delete vs preserve), and forking behavior. Wild's recent optimizations like fallocate and hugepages will improve performance on non-tmpfs filesystems.
Wild and Mold linkers were benchmarked with substantially different configurations, including filesystem type (tmpfs vs ext4), output file handling (preserved vs deleted), and fork behavior, explaining performance discrepancies between their published results. Wild performs better with tmpfs and preserved output files, while Mold's ext4 benchmarks reflect typical user environments more accurately.