We’ve wrapped up the latest performance improvements mentioned above. 3.3-beta.1 is coming soon, we’re just revisiting the docs, testing, addressing some feedback, and clearing up a few remaining issues.
We’ve received private profiles that helped us understand different setups and gather focused feedback. This has been really helpful to see how updates behave in various environments. Thanks to everyone who tested early. 
Here’s a quick look at how the numbers shift from 3.2 and 3.3-beta.0 in the upcoming 3.3-beta.1.
Results are from fredmaiaarantes/simpletasks app on a specific machine, and using Meteor checkout
An issue in published Meteor version was also fixed, so using it when published should show more noticeable performance gains than checkout results above.
We are likely hitting already performance improvement limits on Meteor 3.3, or at least, we consider it sufficient for now. Meteor 3.4 will push those numbers down further, as more of the app’s code and dependencies processes, like watching, transpiling, compiling, and minifying, will be delegated to a modern bundler. That will allow Meteor concentrate on what matters: Atmosphere packages, dev server app, Mongo dev server, CLI, produce the final bundle and other specifics.