Blog: https://ai.googleblog.com/2017/07/revisiting-unreasonable-ef...
Blog: https://ai.googleblog.com/2017/07/revisiting-unreasonable-ef...
In fact, unless the cost of adding and using training data exponentially decreases over time, it's a mathematical certainty that a logarithmically increasing n will quickly incur expensive, diminishing returns for using more data.
So in the context of this Google paper, you could conceive of a situation where training data actually becomes easier to load (albeit subexponentially) and still becomes too expensive to use relatively quickly.
So in point of fact, according to the cited paper Google is asserting there are diminishing returns to increasing the volume of data.
The headline of this article is "More data is not better", which is a stronger claim than diminishing returns - it's neutral or negative returns.
* As the number of product data grows, the benefits were negligible
* More observations per product was important
* The results were consistent with asymptotic theory (central limit theorem) that predicts that more data has diminishing returns.
In any case, this seems to be a case of "diminishing returns."
Well, if I was paying $10,000 for 10,000 examples (to collect, cleanup, process, train with, etc), getting 90% accuracy and making $90,000 from the training model, and now I'm paying $10,000,000 for 10,000,000 examples, getting 91% accuracy and making $91,000 from the trained model, I'm losing money where before I was making some. That's "not better".
Anyway, the cost per example doesn't have to be astronomical. If you need a few millinos of those, you can pay a fraction of a penny and still have a big black hole in your budget, unless you can significantly improve performance.
To give you a sense of how cheap computing power is, my startup regularly processes roughly 2B webpages with some complicated algorithms that need to go node-by-node over the whole DOM tree. That's roughly 77TB of (gzipped) data, and around 100 trillion nodes. It costs me a few hundred bucks of AWS time. That's a rounding error for a big corp; a single data scientist's salary for one day will run you around that much.
Logarithmic growth slows down, but not asymptotically. Think about it: what would the asymptote be? (There is none.)
Well, in that context every kind of (monotonic) growth is asymptotic, so the word has no meaning.
Since you made the correction you're probably already familiar with these, but for the benefit of others: https://en.wikipedia.org/wiki/Slowly_varying_function
If a 5% increase in accuracy worth more than the cost of data storage and computation then it's a pretty clear win.
It would be interesting if there was some corresponding law for more flexible models which did indeed give you logarithmic scaling.