3 ms·
Exactly, what people seem to be doing is mistaking beautiful elegant code as the aim which it isn't. Sure we all love fast well designed code but all we care ab
by hartror 17y ago
Exactly, what people seem to be doing is mistaking beautiful elegant code as the aim which it isn't. Sure we all love fast well designed code but all we care about is getting the users page to them as fast as possible with the minimum fuss.
If it takes more than one line to write or read or invalidate your cache you are doing it wrong (or your framework is doing it wrong). (Same with your split tests, you split test right? . . right?).
- prodigal_erik 17y agoDoing it in one line sounds like accessing a single cache slot at a time. We found we're a lot better off collecting the set of cache slots we need and then fetching them all in parallel, rather than waiting until we have the result for slot #1 before we can even start the request for slot #2. Every transaction is at least two context switches, sometimes worse.