A few month ago, I used a similar optimisation that does the same idle-awaiting but with server-requests instead of cpu-usage.
So instead of submitting all ajax to the server directly, background tasks can be delayed until the important tasks have finished. This is useful especially when the 6 requests per origin limit gets hit often.
I tested this with docker and could not observe a big performance-penalty on the cpu usage. Of corse you need more memory and the biggest thing is that you have to build your application in a way that you can do this later.
Meteor has the op-log-driver which calculates query-result for changes instead of running the wohle query again. Same comes with rxdb where it's called query-change-detection.
That's true, but monitoring the stream of change events in a single machine (be it server or client) makes this machine your bottleneck for overall system throughput.
That isn't how supply and demand and market liquidity works.
This is why institutional traders have to break up buys or sells over many transactions. If you put up a huge block saying "I want to buy/sell $X million / Y million units of instrument Z" it is going to strongly drive the market away from your bid/ask. In a market like BTC, it might drive the price down 50% within minutes.
In other words, who is going to be on the other side of your market? If you are selling 1000 BTC, and if the top bid price has a quantity of 0.1 BTC, you will blow through the first level, then the second, thrid, etc, through dozens of decreasing price levels, if you are doing market orders. You will take out the ENTIRE BUY SIDE OF THE MARKET, and the price of your last transaction will be thousands of dollars lower than the first price. If you are doing a limit order, then you provide the lowest price you are willing to go, so you might only be able to sell a few coins.
I worked in many teams and projects. Each time we had a "rockstar" in the team, he was worth more than 3 regular guys.
In the last project most echnical decisions where made/influenced by the rockstar and we saved so much time with playing arround or programming things that brake in the future.
As a recruiter I would never hire rockstars-only. But I would definitely make sure that I have a good ratio of them.