Use optimistic functions with assets #10452
Meteor currently reads and hashes each asset during every build. The watcher then uses the optimistic functions to read and hash the file, which stores a copy of the contents in memory. During rebuilds it then reads the file again, causing multiple copies of the file to be in memory.
This changes it to always use optimistic functions with assets. Starting with the second rebuild, this saves 1.5 - 2 seconds of garbage collection during each rebuild in one app in addition to not having to read or hash the files.
An alternative is to use
The text was updated successfully, but these errors were encountered: