World-writable memory on Samsung Android phones
Posted Dec 26, 2012 18:20 UTC (Wed) by khim
In reply to: World-writable memory on Samsung Android phones
Parent article: World-writable memory on Samsung Android phones
I'd say that most release managers won't even ask you about resources,
Well, I guess we are living in totally different worlds. In my company "resources requirement" is one of the most important items in the release process.
let alone refuse to accept something without the requirements tightly specified.
Who said anything about "tightly specified"? It depends on what we are releasing. If it's some addon to the 100'000 servers cluster which produces better statistic then estimate “will need no more then one additional server of regular capacity” may be perfectly good estimate but if it's something like “will need additional 3% of RAM” then it may be a big deal (3% of RAM will mean 3'000 new servers and these are expensive enough to warrant further look).
In the end it's all about the money: if money lost (or “found” if we are measuring sales) are below certain threshold then, of course, resource consumption becomes a moot point, but when we are talking about services which have hundred millions of users then this threshold can be surprisingly low.
Yes, there are times when the resource utilization really matters, but much of the time it doesn't matter that much, and other pressures (like time to market) matter much more.
My experience is direct opposite. Yes, sometimes you only need rough estimate and don't care about 2x difference in memory or speed but you always care about 1000x difference. And O(N²) instead of O(N) can produce 1000x difference pretty easily (while JIT-introduced memory consumption rarely produce more then 2x difference… latency is much bigger problem when JITs and GCs are involved).
to post comments)