> Normally for multiple teams with heavy traffics, Wey should not have any significant CPU usage, and RAM ussage is usually under 100MB. However if you have a team with more than 10k users in it, the memory usage may increase a lot.
Bloaty technologies was what made MS great in the 80's/90's, because 18 months later, the speed of the CPU would double.
I feel like we should think hard about optimizing for memory/cpu again.
Transistors can stay the exact same size for twenty years as long as the die size grows, and Moore’s law still holds.
https://www.anandtech.com/show/5261/amd-radeon-hd-7970-revie...
But again, did transistors double in count on any processor, not just GPUs? If so, Moore held. Yes, according to this chart:
https://en.m.wikipedia.org/wiki/Moore's_law#/media/File%3AMo...
It's meaningless to compare these totally different types of chips that end up with extremely different transistor densities on the same node due to the wiring requirements.
Are there no CPUs with higher transistor counts out there? Maybe ones you are not aware of yet?
That was my question to you. You claimed, "It's 2018 and the top chip on that chart still has the highest transistor count of any CPU on the market." Which I take to mean that you don't know of any CPU with any higher transistor counts, which is an argument from silence. There could be a CPU outside of your knowledge.
So, we wait to see. Moore may be dead but "moore" time may be needed to hold the funeral.
It is too early to declare Moore's Law dead.
You say that like people were making these bloaty apps for the good of humanity—trying to make them objectively perfect, but falling short. While FOSS is done with that mindset, FOSS isn’t usually where bloat comes from.
Bad engineering is usually the result of overriding business concerns: being first to market, iterating quicker than your competitors, having more reach on more platforms with less expense, etc. More features before feature polish, and user-visible polish before good architecture.
Even without Moore’s law, this incentive is still in place. It not just has a slight countervailing force of nobody wanting to run apps that take too many resources.
What that means in practice is that apps will still be as bloated as possible (or rather, with as little optimization done as possible) while still managing to not choke the machines they’re on.
Can't make transistors smaller? just add more! Speed of light becoming a problem? Stack em! Speed of light and heat becoming a problem again? Stack cores, improve multi-core architecture in both hardware/software and enjoy another many decades of Moore's law. It won't be dieing any time soon
Wikipedia:
Moore's law is an observation and projection of an historical trend and not a physical or natural law. Although the rate held steady from 1975 until around 2012, the rate was faster during the first decade. In general, it is not logically sound to extrapolate from the historical growth rate into the indefinite future. For example, the 2010 update to the International Technology Roadmap for Semiconductors, predicted that growth would slow around 2013, and in 2015 Gordon Moore foresaw that the rate of progress would reach saturation: "I see Moore's law dying here in the next decade or so."
Intel stated in 2015 that the pace of advancement has slowed, starting at the 22 nm feature width around 2012, and continuing at 14 nm. Brian Krzanich, CEO of Intel, announced, "Our cadence today is closer to two and a half years than two." Intel is expected to reach the 10 nm node in 2018, a three-year cadence. He cited Moore's 1975 revision as a precedent for the current deceleration, which results from technical challenges and is "a natural part of the history of Moore's law."
More background in recent article here on 40 years of processor performance:
https://www.eejournal.com/article/fifty-or-sixty-years-of-pr...