I looking on the web I added the library path to this.env.noParse in base_optimizer.js but it is not improving the optimizer time. If anyone has any ideas that be great. Sadly I can not change the library code.
Is this for a deployment or in development mode? In either case I'd recommend atleast 4GB of ram for the machine installing the plugin.
For production you can optimize on a beefier machine and then zip the whole package up for sending to a more resource constrained server.
For development I'd have to dig further if hardware isn't the cause. Bumping max old space size is worth a try (
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.