Deutsch English Français Italiano |
<20240529130818.000070bf@yahoo.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Michael S <already5chosen@yahoo.com> Newsgroups: comp.lang.c Subject: Re: xxd -i vs DIY Was: C23 thoughts and opinions Date: Wed, 29 May 2024 13:08:18 +0300 Organization: A noiseless patient Spider Lines: 55 Message-ID: <20240529130818.000070bf@yahoo.com> References: <v2l828$18v7f$1@dont-email.me> <00297443-2fee-48d4-81a0-9ff6ae6481e4@gmail.com> <v2lji1$1bbcp$1@dont-email.me> <87msoh5uh6.fsf@nosuchdomain.example.com> <f08d2c9f-5c2e-495d-b0bd-3f71bd301432@gmail.com> <v2nbp4$1o9h6$1@dont-email.me> <v2ng4n$1p3o2$1@dont-email.me> <87y18047jk.fsf@nosuchdomain.example.com> <87msoe1xxo.fsf@nosuchdomain.example.com> <v2sh19$2rle2$2@dont-email.me> <87ikz11osy.fsf@nosuchdomain.example.com> <v2v59g$3cr0f$1@dont-email.me> <20240528144118.00002012@yahoo.com> <v34odg$kh7a$1@dont-email.me> <20240528185624.00002494@yahoo.com> <v359f1$nknu$1@dont-email.me> <20240528232315.00006a58@yahoo.com> <v35qrg$qhnf$1@dont-email.me> <v36p6t$12k77$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Wed, 29 May 2024 12:08:08 +0200 (CEST) Injection-Info: dont-email.me; posting-host="cc56f7764e2eeae1c5e3f45aa7e89a16"; logging-data="1144388"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18JzWpbdbaFmX13vpLAdGggSsUmLMhutSs=" Cancel-Lock: sha1:ykdEdtaRY2vw+ScZW3+zysQgFnM= X-Newsreader: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32) Bytes: 3842 On Wed, 29 May 2024 10:32:29 +0200 David Brown <david.brown@hesbynett.no> wrote: > On 29/05/2024 01:54, bart wrote: > > On 28/05/2024 21:23, Michael S wrote: > >> On Tue, 28 May 2024 19:57:38 +0100 > > > >>> OK, I had go with your program. I used a random data file of > >>> exactly 100M bytes. > >>> > >>> Runtimes varied from 4.1 to 5 seconds depending on compiler. The > >>> fastest time was with gcc -O3. > >>> > >> > >> It sounds like your mass storage device is much slower than aging > >> SSD on my test machine and ALOT slower than SSD of David Brown. > > > > David Brown's machines are always faster than anyone else's. > > That seems /highly/ unlikely. Admittedly the machine I tested on is > fairly new - less than a year old. But it's a little NUC-style > machine at around the $1000 price range, with a laptop processor. > The only thing exciting about it is 64 GB ram (I like to run a lot of > things at the same time in different workspaces). > Modern laptop processors with adequate cooling can be as fast as desktop (and faster than server) for a task that uses only 1 or 2 cores. Especially when no heavy vector math involved. If the task runs only for few seconds, like in our tests, then they CPU can be fast even without good cooling. And $1000 is not exactly low price for mini-PC without display. Last time I bought one for my mother, it costed ~$650 including Win11 Home Ed. > But I am better than some people at getting my machines to run > programs efficiently. I don't use Windows for such things (I happily > run Windows on a different machine for other purposes), and I > certainly don't use layers of OS or filesystem emulation such as WSL > and expect code to run at maximal speed. > WSL would not affect user-level CPU-bound part and even majority of kernel-level CPU-bound parts. It can slow down I/O, yes. But it turned out (see my post above) that the bottleneck was in CPU. > And as I said in an earlier post, I didn't have the files on any kind > of disk or SSD at all - they were all in a tmpfs filesystem to > eliminate that bottleneck. > You should have said it yesterday.