Thomas Camlong
5fb8e9223a
Closes the largest unexplained item in the peak breakdown, then closes it off as a lever. Attribution: peak_malloced_memory goes 4.5 -> 42.1 MiB the moment a board's modules compile, while current malloced_memory stays at 1.0 - memory V8 takes to compile, frees back to malloc, and musl never returns to the kernel. Confirmed by re-reading the --jitless runs, where the spike never occurs at all (4.5 MiB at every stage). --jitless is unusable because it under-renders the page, but V8 can cap the optimisation tier instead of removing codegen. --max-opt is rejected by NODE_OPTIONS and accepted on the command line, so it was wired behind HOMARR_MAX_OPT and A/B'd on one image: peak anon 276.0 -> 282.8 MiB (+2%) boot idle 64.0 -> 72.3 MiB (+13%) board loaded 186.1 -> 179.2 MiB (-4%) 4 tabs 270.8 -> 238.5 MiB (-12%) after soak 199.0 -> 214.3 MiB (+8%) CPU 28.1 -> 27.8 s (unchanged) Null result. Render integrity was verified explicitly this time - listeners 7,784 in all four runs, DOM nodes within 40 - so unlike jitless the page rendered fully and the comparison is valid. The mechanism explains it: measured under --max-opt=2, peak_malloced_memory at board load is 42.1 MiB, identical to Turbofan. Maglev's zones are just as large. Capping the tier does not reduce zone memory; only not compiling does, and that breaks rendering. So this 38 MiB is not reachable through V8 configuration. It scales with how much JavaScript V8 must compile, which returns it to the single remaining server-side lever: ship less server code. Reverted.
Live Demo 🎮 • Install 💻 • Translations 🈺 • Discord 👋
- 🖌️ Highly customizable with an extensive drag and drop grid system
- ✨ Integrates seamlessly with your favorite self-hosted applications
- 📌 Easy and fast app management - no YAML involved
- 👤 Detailed and easy to use user management with permissions and groups
- 👥 Support for single sign on via OIDC / LDAP
- 🙊 Safe encryption using BCrypt and AES-256-CBC for your valuable data
- 🕔 Realtime widget updates using WebSockets, tRPC and Redis
- 🔍 Search through thousands of data points in supported integrations or your data in Homarr using the fast built-in search
- 🦞 Icon picker with over 11K icons
- 🚀 Compatible with any major consumer hardware (x86, Raspberry Pi, old laptops, ...) and most OS (Windows, Linux, TrueNAS, Unraid)
- 🖥️ Extensive Kubernetes support with Helm for efficient scaling & high reliability
Please click here for official installation instructions
Homarr is a free-to-use open source project maintained by volunteers and developers from all over the world.
We publish under the Apache License 2.0 license which allows commercial usage.
We invest multiple hours daily in providing support, developing Homarr, integrating to third party software and more.
We also pay for licensing and server hosting fees.
Please consider helping us cover these costs to enable the future development of Homarr. Thank you!
Please click here to sponsor us at OpenCollective
You can also support us by helping with translating the entire project to as many languages as possible or contributing directly to the code or documentation. Please read our Contribution Guidelines. All contributions, regardless of their size or scope, are welcome and highly appreciated! Thank you ❤️
Sponsors
Thanks to your generous sponsors, we can continue to build Homarr. Check them out for high-quality and easy-to-use development tools. Feel free to contact us at homarr-labs@proton.me if you wish to become a sponsor.
