3 ms·
Ah, yes. In a parallel programming class at the moment and now I can't stop thinkin about cache boundaries, volatility, weird efficient instructions to use.. Is
by bm1362 14y ago
Ah, yes. In a parallel programming class at the moment and now I can't stop thinkin about cache boundaries, volatility, weird efficient instructions to use.. Is this false sharing and throwing out the cache line? Where can I use rsqrtf? Am I utilizing the SM fully? Is this busy-wait killing the memory controller?
It goes on forever.
- stelonix 14y agoBoth of you talk as if generally, people never worry about such things. It seems unusual to me. Is it because the first language I learned was 65816 assembler?
- chc 14y agoIn domains where fine-grained performance is not paramount (i.e. most programs), no, people don't worry about that sort of thing very much. How do you even go about reasoning on cache lines in a Ruby on Rails app?
- ajross 14y agoPeople never worry about machine-level micro-optimizations in exactly the same that people never worry about MVC web app frameworks, which is to say "most people almost never" for some appropriate metric for "most" and "almost". It's a niche. My point was just that some people are happy in just one, while others (the poster I was replying to, and myself among them) aren't.