News for hackers. Stuff that matters.
Re:The problem with reinforced concrete by Retric on Saturday June 25, 2016 @03:09PM (#11977535)
I have optimized websites based on a basic understanding of how CPU's work before. For example it's much faster to do 200 checks on an object then load the next object vs doing one check at a time for each object and thus reloading objects 200 times. This ended up being a 30x or so speed up and seemed like magic to half the room.

It's not about knowing the minute details so much as understanding what's going on well enough to model it in your head.

PS: Assuming you are operating on lots of data, a small scale test can and did go the other way.

Re:The problem with reinforced concrete by agumonkey on Sunday June 26, 2016 @09:05AM (#11980595)
Good thinking but beware of what a CPU "is". I've just came back from intel.com boards and .. holy jesus, amount of details even memory locality level thinking ignores .. To leverage a processor you need to understand OS cache conventions and interaction with L1 and L2 caches and how these caches are wired to the actual core. Otherwise you're already losing 30% of the raw bandwidth.

I left with a strong laziness view on optimization. Profile based on what the business needs and ignore everything else or you will never escape the rabbit hole.

Re:The problem with reinforced concrete by Tiquor on Saturday June 25, 2016 @03:19PM (#11977581)
Most people wouldn't know an algorithm and concepts of algorithmic complexity if it bit them on the ass. Even devs. You don't need a PHD in computer science, just read some stuff and think a bit.
Re:The problem with reinforced concrete by hinkley on Monday June 27, 2016 @01:51AM (#11984390)
The number of people I've had to explain reflow to is just staggering.