News for hackers. Stuff that matters.

A comment on What every programmer should know about memory, Part 1. Parent comment

Re:What every programmer should know about memory, Part 1 by shabble on Wednesday May 02, 2012 @11:06PM (#3922200)
Wouldn't you rather have at least an approximate map showing the more swampy areas on your random walk up Performance Mountain (or is it down into Performance Valley? The sight of all these top-rooted trees is confusing me)?
[ Parent | on HN ]
Re:What every programmer should know about memory, Part 1 by barrkel on Thursday May 03, 2012 @03:43AM (#3922812)
I'm criticizing basing your architectural decisions on things as low-level as specific DRAM timings, unless perhaps you're targeting a very focused, extremely mass market niche, like a console.

I never said that one must be ignorant of factors that can affect performance when measuring. Rather, don't try and predict from first principles without measuring.

[ Parent | on HN ]