Slow Performance on AWS Lambda about webpack-isomorphic-tools HOT 3 CLOSED

Well, when you call require() which is overrided it simply takes the value from webpack-assets.json and returns it.
In production this file is loaded and parsed a single time and then cached.
There should be no bottleneck.

You can test for a bottleneck more precisely if you do, say,

console.log(new Date())
require('./asset.css')
console.log(new Date())

from webpack-isomorphic-tools.

Uggg...sorry for this. I tried tons of stuff, removing the babel runtime and getting rid of babel using bluebird for promises and just using the babel-polyfill. The best result was getting rid of isomorphic-tools entirely along with all those other changes but only got it down to 32 seconds.

What ended up being the issue is that the lambda memory had to be cranked up. I was on 128MB and went up to the max of 1536MB then it ran in 3 seconds.

Sorry for opening an unrelated issue but maybe it will help someone else out in the future.

Here is a gist of all of the use cases I tried

https://gist.github.com/dtothefp/0f07b05bba1edc119a6f

from webpack-isomorphic-tools.

oh, I see, pagefile swapping...
that was unobvious.
that what distincts a machine from a human body: you may never know what's going on under the hood.
monitoring systems still have a long way to go.

from webpack-isomorphic-tools.