| Deutsch English Français Italiano |
|
<20250207124138.00006c8d@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!eternal-september.org!.POSTED!not-for-mail From: Michael S <already5chosen@yahoo.com> Newsgroups: comp.arch Subject: Re: Cost of handling misaligned access Date: Fri, 7 Feb 2025 12:41:38 +0200 Organization: A noiseless patient Spider Lines: 47 Message-ID: <20250207124138.00006c8d@yahoo.com> References: <5lNnP.1313925$2xE6.991023@fx18.iad> <vnosj6$t5o0$1@dont-email.me> <2025Feb3.075550@mips.complang.tuwien.ac.at> <wi7oP.2208275$FOb4.591154@fx15.iad> <2025Feb4.191631@mips.complang.tuwien.ac.at> <vo061a$2fiql$1@dont-email.me> <20250206000143.00000dd9@yahoo.com> <2025Feb6.115939@mips.complang.tuwien.ac.at> <20250206152808.0000058f@yahoo.com> <vo2iqq$30elm$1@dont-email.me> <vo2p33$31lqn$1@dont-email.me> <20250206211932.00001022@yahoo.com> <vo36go$345o3$1@dont-email.me> <20250206233200.00001fc3@yahoo.com> <vo4lvl$3eu3c$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Fri, 07 Feb 2025 11:41:43 +0100 (CET) Injection-Info: dont-email.me; posting-host="00fdef6cacc03a422777e88dfabbf73f"; logging-data="3617268"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/W7saB4YzP2tUOrkGtLcZpQqThwEluccQ=" Cancel-Lock: sha1:n0M0spTKlQNZF4k/r0Z8AuSjA5s= X-Newsreader: Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32) Bytes: 3108 On Fri, 7 Feb 2025 11:06:43 +0100 Terje Mathisen <terje.mathisen@tmsw.no> wrote: > Michael S wrote: > > On Thu, 6 Feb 2025 21:36:38 +0100 > > Terje Mathisen <terje.mathisen@tmsw.no> wrote: > >> BTW, when I timed 1000 calls to that 5-6 us program, to get around > >> teh 100 ns timer resolution, each iteration ran in 5.23 us. > > > > That measurement could be good enough on desktop. Or not. > > It certainly not good enough on laptop and even less so on server. > > On laptop I wouldn't be sutisfied before I lok my program to > > particualr core, then do something like 21 measurements with 100K > > calls in each measurement (~10 sec total) and report median of 21. > > Each measurement did 1000 calls, then I ran 100 such measurements. > The 5.23 us value was the lowest seen among the 100, with average a > bit more: > > > Slowest: 9205200 ns > Fastest: 5247500 ns > Average: 5672529 ns/iter > Part1 = 3338 > > My own (old, but somewhat kept up to date) cputype program reported > that it is a "13th Gen Intel(R) Core(TM) i7-1365U" according to CPUID. > > Is that sufficient to judge the performance? > > Terje > Not really. i7-1365U is a complicated beast. 2 "big" cores, 8 "medium" cores. Frequency varies ALOT, 1.8 to 5.2 GHz on "big", 1.3 to 3.9 GHz on "medium". As I said above, on such CPU I wouldn't believe the numbers before total duration of test is 10 seconds and the test run is locked to particular core. As to 5 msec per measurement, that's enough, but why not do longer measurements if you have to run for 10 sec anyway?