search for: rpmalloc

...ult, link times with ThinLTO are extremely slow on Windows. We're observing performance inversely proportional to the number of cores. The more cores the machines has, the slower ThinLTO linking gets. We've replaced the CRT heap allocator by modern lock-free thread-cache allocators such as rpmalloc (unlicence), mimalloc (MIT licence) or snmalloc (MIT licence). The runtime performance is an order of magnitude faster. Time to link clang.exe with LLD and -flto on 36-core: Windows CRT heap allocator: 38 min 47 sec mimalloc: 2 min 22 sec rpmalloc: 2 min 15 sec snmalloc: 2 min 19 sec We...

...ult, link times with ThinLTO are extremely slow on Windows. We're observing performance inversely proportional to the number of cores. The more cores the machines has, the slower ThinLTO linking gets. We've replaced the CRT heap allocator by modern lock-free thread-cache allocators such as rpmalloc (unlicence), mimalloc (MIT licence) or snmalloc (MIT licence). The runtime performance is an order of magnitude faster. Time to link clang.exe with LLD and -flto on 36-core: Windows CRT heap allocator: 38 min 47 sec mimalloc: 2 min 22 sec rpmalloc: 2 min 15 sec snmalloc: 2 min 19 sec We...

...As a result, link times with ThinLTO are extremely slow on Windows. We’re observing performance inversely proportional to the number of cores. The more cores the machines has, the slower ThinLTO linking gets. We’ve replaced the CRT heap allocator by modern lock-free thread-cache allocators such as rpmalloc (unlicence), mimalloc (MIT licence) or snmalloc (MIT licence). The runtime performance is an order of magnitude faster. Time to link clang.exe with LLD and -flto on 36-core: Windows CRT heap allocator: 38 min 47 sec mimalloc: 2 min 22 sec rpmalloc: 2 min 15 sec snmalloc: 2 min 19 sec We’r...

...dows. We’re observing performance inversely proportional to the >> number of cores. The more cores the machines has, the slower ThinLTO >> linking gets. >> >> >> >> We’ve replaced the CRT heap allocator by modern lock-free thread-cache >> allocators such as rpmalloc (unlicence), mimalloc (MIT licence) or snmalloc >> (MIT licence). The runtime performance is an order of magnitude faster. >> >> >> >> Time to link clang.exe with LLD and -flto on 36-core: >> >> Windows CRT heap allocator: 38 min 47 sec >> >>...

...to the >>>> number of cores. The more cores the machines has, the slower ThinLTO >>>> linking gets. >>>> >>>> >>>> >>>> We’ve replaced the CRT heap allocator by modern lock-free thread-cache >>>> allocators such as rpmalloc (unlicence), mimalloc (MIT licence) or snmalloc >>>> (MIT licence). The runtime performance is an order of magnitude faster. >>>> >>>> >>>> >>>> Time to link clang.exe with LLD and -flto on 36-core: >>>> >>>> Wind...

Hey list, TL;DR - LLVM 10 is around 7-8% slower than LLVM 9 when compiling the same inputs. So here at Unity our Burst HPC# compiler uses LLVM to provide our users with some very optimal codegen. LLVM is used in two ways: 1. In the Unity editor we JIT compile user code. 2. We also have an AOT mode for when our users are building a full game. Particularly for 1., compile time really matters for