Description
Hi,
while watching the build of rust 1.73.0 on the various NetBSD targets we support via our packaging system pkgsrc, some of those targets slower than others, it appears to me that somewhat surprisingly, the rust-installer program is perhaps the most resource hungry in terms of virtual memory of all the processes used to complete a build and installation. On amd64, I've seen it balloon to 1.8GB, and on 32-bit armv7, I've observed it ballooning to 1.5GB. I predict that unless something is done to reign in and/or optimize the virtual memory consumption of rust-installer, it is going to be the first process which causes rust to no longer to be possible to build (and install) natively on various 32-bit platforms. If I'm not terribly mistaken, e.g. NetBSD's armv7 port(s) have an upper bound on user-mode virtual memory when executed on 32-bit hardware of somewhere in the area around 1.8GB.
I'll admit that I have not (yet) looked closely at what it is that rust-installer does which causes it to behave in this manner, or the particular way it goes about doing this, and therefore have no concrete suggestion for what needs to be improved / optimized or done differently.
Input solicited on whether this is easy, difficult or near-impossible to do anything about this issue.