| 21 Oct 2025 |
Julian | I created a respective issue, highlighting the I suppose actual root cause, all things considered https://github.com/NixOS/nix/issues/14317 | 17:03:51 |
dramforever | In reply to @juliankuners:matrix.org I created a respective issue, highlighting the I suppose actual root cause, all things considered https://github.com/NixOS/nix/issues/14317 oh yeah that's a duplicate of https://github.com/NixOS/nix/issues/13698 | 17:13:40 |
dramforever | guess i was a few hours late to the discussion | 17:15:47 |
Julian | Thank you, I missed this one during my issue search. I closed it and linked to it in the respective other issue. | 17:19:57 |
| @echobc:matrix.org joined the room. | 18:09:44 |
| NixOS Moderation Bot banned @echobc:matrix.org (<no reason supplied>). | 18:09:44 |
Eelco | learned today that using std::string for large buffers is very inefficient (huge kernel overhead): https://github.com/DeterminateSystems/nix-src/pull/238/commits/edf45d6e1158a059e7ded5460d2a3947dc35fdf8 | 20:44:48 |
Sergei Zimmerman (xokdvium) | This is sort of more about doing unnecessary construction/destruction of an object. Not special to std::string in any way | 20:55:40 |
Eelco | it's a result of having a large contiguous allocation (so it would also affect std::vector<char>) | 20:56:21 |