| Deutsch English Français Italiano |
|
<1029gg4$1a6m8$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Muttley@DastardlyHQ.org Newsgroups: comp.lang.c Subject: Re: encapsulating directory operations Date: Tue, 10 Jun 2025 14:46:28 -0000 (UTC) Organization: A noiseless patient Spider Lines: 20 Message-ID: <1029gg4$1a6m8$1@dont-email.me> References: <100h650$23r5l$1@dont-email.me> <10229vo$3b858$1@dont-email.me> <102497b$3tavs$3@raubtier-asyl.eternal-september.org> <Qij1Q.929648$mjgd.612014@fx09.iad> <1024qkl$1iim$3@raubtier-asyl.eternal-september.org> <VOB1Q.374963$K3w3.304119@fx05.iad> <1026uas$k2dv$1@raubtier-asyl.eternal-september.org> <PrD1Q.104796$9QV5.36641@fx39.iad> <10276jc$lt1o$1@raubtier-asyl.eternal-september.org> <6OF1Q.1173207$%pKb.770421@fx14.iad> <1028mds$13ut7$1@dont-email.me> <whW1Q.1087624$qmJf.227448@fx16.iad> Injection-Date: Tue, 10 Jun 2025 16:46:28 +0200 (CEST) Injection-Info: dont-email.me; posting-host="5d9373d65cc16eb7707f6cb135bbf0a9"; logging-data="1383112"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/uwvAPJSW79R083q5ksh4b" Cancel-Lock: sha1:Y6k8cv/0kqw9Iid1AsBhLF1mKPA= 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.