5 ms·
"Fix" how exactly? I'm not quite sure what you're suggesting.
by gipp 4y ago
"Fix" how exactly? I'm not quite sure what you're suggesting.
- jeffbee 4y agoC++ proto reflection is a convenience. If it actually shows up at scale in production, that smells like a design error.
- moultano 4y agoAll things show up at scale in production at Google.
- jeffbee 4y agoIn one sense yes, but in another sense even though Google is large their threshold for something being worth fixing based on efficiency justifications is correspondingly large.
- foota 4y agoFrequently though, you're dealing with a death by a thousand paper cuts. Perhaps that call comes from some common library whose implementation requires reflection.
- moultano 4y agoIt isn't though. A typical developer will never care about 0.1% of unnecessary CPU usage in their application, but at Google, depending on what component it's in, that can easily be a million dollar find.
- jcelerier 4y ago> In one sense yes, but in another sense even though Google is large their threshold for something being worth fixing based on efficiency justifications is correspondingly large. not everything is a linear relationship
- usefulcat 4y agoIf you're measuring in terms of time, electricity, or hardware, then the threshold would tend to be lower for Google, not higher. A 0.1% savings on a million machines is ~1 million times more valuable than a 0.1% savings on a single machine. OTOH if the measurement is risk of breaking something, then it's not nearly so clear, since larger organizations tend to have more software and hardware, and therefore more opportunities for things to get broken.
- jeffbee 4y agoYou're saying the opposite of what the other guy said, though. They said that at scale small things are big. I'm saying that at scale .001% is still .001%.