>>37143
>aaaa you made it worse
Haha, sorry Anon. :^) And actually, that was slightly-intentional, in an effort to 'complexify' the problemspace being tested by this simple harness.
>its not really a compiler or algorithm thing its the fact the cpu stalls waiting on ram cuz all youre really doing is reading from memory
Yeah, I can totally see that. Kinda validates my earlier claim that
>"...my test is too simplistic really."
>youre not clearing the cache in your test, everything after the first test has the advantage of having parts preloaded in the cache
This would certainly be a valid concern in a rigorous test-harness. OTOH, I consider it a relatively negligible concern in this case. After all, the caches are quite smol in comparison to a 100M (8byte+8byte) data structure? (However, it probably
does explain the
'very slight edge' mentioned earlier for the standard form of find_if [and, by extension, which
doesn't occur for the more complex data-access strategy of the parallel version of it].)
<--->
Regardless, I think this simple testing here highlights that fact that for
simple data firehose'g, the compiler will optimize away much of the distinctions between different architectural approaches possible.
I don't see any need to test this further until a more-complex underlying process is involved. Cheers, Anon.
Message too long. Click
here
to view full text.
Edited last time by Chobitsu on 02/22/2025 (Sat) 17:27:02.