Date: Fri, 13 Sep 2024 11:28:43 +0000 From: Paul Floyd <paulf2718@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: The Case for Rust (in any system) Message-ID: <e417c155-0186-4694-bb9b-7fdf7b94b96c@gmail.com> In-Reply-To: <2EE309BF-CE1D-48AD-9C53-D4C87998B4A0@freebsd.org> References: <CAOzHqcJ0rOR4CoL84WgZQNcgY2G9vuiHccE4XT_otJ2R51KJ3Q@mail.gmail.com> <2EE309BF-CE1D-48AD-9C53-D4C87998B4A0@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13-09-24 06:17, David Chisnall wrote: > On 13 Sep 2024, at 02:34, Joe Schaefer <joesuf4@gmail.com> wrote: >> >> I just completed a month long project to port a C++ codebase that used vectors for array allocations back to using C‘s calloc. For a 15% increase in memory footprint, batch jobs that took three days to complete now finish in 10-12 hours. > > This sounds highly dubious given that std::vector is a very thin wrapper around malloc. From your description, I would expect the same speedup with some judicial use of .reserve(). And I forgot to say. I'm sure that John Lakos has an opinion on the use of PMR that could well be applicable in this case. Does Rust have anything like PMR? A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e417c155-0186-4694-bb9b-7fdf7b94b96c>