-
Notifications
You must be signed in to change notification settings - Fork 380
server task takes 2-7min to complete #42
Comments
Hugo bin on its own can tear through 1,000 pps like butter when run on HDD. My take is the JS is the bottleneck as the code isn't compiled – it's interpreted. |
I've seen very large sites run locally and never anything like this. Can you provide more details so we can reproduce? Is your repo public? |
Sorry @erquhart it isn't public. We use Hugo's partials functionality no templates, and we copy js files instead of using webpack. Here's the latest:
Would sharing the config file help? |
Considering the number of files you're watching, this might be par for the course. The hugo task I'm using isn't stock, so that takes longer, but the rest is pretty much the same - here's what I'm seeing with a large site, but with considerably less files than yours:
Perhaps there are ways to optimize the pipeline, or just get rid of gulp and use webpack (not certain it would be faster, but maybe so). |
Closing this due to age, comment if you want to revive. |
Is it normal to have the server task take 2 to 7 minutes to complete (depends on the machine I use)?
Consider that running hugo server directly from the site dir takes less than a second.
[Edit]
tested by commenting out the 'watch' subtasks, it looks like the bottleneck is the gulp watch hugo task.
The text was updated successfully, but these errors were encountered: