Re: encapsulating directory operations

On Tue, 10 Jun 2025 13:19:24 GMT
scott@slp53.sl.home (Scott Lurndal) wibbled:

Muttley@DastardlyHQ.org writes:

Ugh. Then you end up like the Java JVM - grabbing boatloads of memory that
causes huge startup delays and can often cause the machine to do lots of
swapping and/or slow everything else down to treacle.

>
That's a problem with host not being suitable for java, if that
is the behavior you are seeing.  I've not seen that in production
java-based applications that are competently developed.
>
For C/C++, one generally allocates page-aligned regions with mmap, eschewing
granular allocation methods such as new/delete/malloc.

No, one generally doesn't. Why on earth would anyone bother with their own
low level memory allocation based on pages unless they were writing something
like a database? Plus I'm sure most modern implementations of malloc() are
sophisticated enough not to just allocate random blocks of memory but have
their own pool behind the scenes which they manage.