Re-building development bundle step very slow #35911
Labels
stale?
Issue that may be closed soon due to the original author not responding any more.
status: needs reproduction
This issue needs a simplified reproduction of the bug for further troubleshooting.
topic: DX
Developer Experience (e.g. Fast Refresh, i18n, SSR, page creation, starters)
type: bug
An issue or pull request relating to a bug in Gatsby
Comments
oorestisime
added
the
type: bug
gatsbot
bot
added
the
status: triage needed
|
We've got the same result. We were expecting a speed boost from 3->4, but a significant speed downgrade, so we decide no to upgrade until the issue is resolved. gatsby-plugin-sharp.IMAGE_PROCESSING jobs almost take 1 minutes to handle 200 images on M1 macbook air. |
|
|
And still don't know during the developing, I only change a simple text on a markdown file will result a full site building including the slowest gatsby-plugin-sharp.IMAGE_PROCESSING jobs. |
LekoArts
added
status: needs reproduction
|
It's hard to help from the outside without any reproduction. webpack isn't the fastest hot-reloading anymore compared to other solutions so depending on your setup it mights just be the speed -- but it surely also could be something that we can optimize. For example:
This then just means that you have
Some ideas:
|
|
The queries as shown in my logs are pretty fast. Its whatever going on with webpack that is slow. |
|
Ok run it with the options you suggested. Nothing clear cuts for me here. Here's the full run and again i am fine with the time it takes (i mean its not my biggest issue here :D ) aaaand here is the fast refresh update
|
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
github-actions
bot
added
the
stale?
|
I had this issue but it was The plugin caused out-of-memory issues and the file size was massive (over 4GB for a small project). Try disabling the |
github-actions
bot
removed
the
stale?
|
Not using emotion but styled components. We dont have this in our gatsby config. Not sure if styled-components generates sourceMap. I ll check that out thanks! |
|
We also have the exact same issue, the source map option didnt help with the speed |
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
github-actions
bot
added
the
stale?
|
The build is still much slower than gatsby v3. The emotion plugin was a big factor for me but even still it does take a while. Not sure if it's fair to mark it as stale. I think people would like an update on any progress made toward improving the speed of the dev bundle. |
github-actions
bot
removed
the
stale?
We constantly do that when we know the root of the issue which isn't the case here. So there's nothing we can do right now until we have clear indications and explanations to what the issue is (other than "it's slow") |
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
github-actions
bot
added
the
stale?
|
I doubt we are the only ones seeing the dev being so slow. And not sure what else to give as examples. |
github-actions
bot
removed
the
stale?
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
github-actions
bot
added
the
stale?
|
Hey again! It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Preliminary Checks
Description
Since migrating to v4 from v2 we have been experiencing a rather unpleasant local development setup. Everything got slower in building.
I managed to score some easy wins on the
Building development bundle(mainly around mini-css-extract-plugin) and brought it down significantly but theRe-building development bundleis still very slow.Here's an example log. The changes i am doing is copy chaning on our index https://bold.org/
Seems that fast-refresh is not that "fast" :D but more importantly it is very irregular since all the changes shown are the same. Just copy changes.
Reproduction Link
Hard to do
Steps to Reproduce
Can't create minimal reproduction and i understand this is going to be hard to debug. I am willing to join a call and debug through OR getting some help on how to profile those steps to maybe understand what is going on.
I just know that we upgraded to gatsby 4 and this started. I ve been debugging this for 2 days and can't get to anything related to fast-refresh. Managed to improve only the cold and warm boots.
Expected Result
Fast refresh should be around 1 second
Actual Result
Fast refresh is at 1-7 seconds locally
Environment
Config Flags
PRESERVE_FILE_DOWNLOAD_CACHE: true,
FAST_DEV: true,
PARALLEL_SOURCING: true,
The text was updated successfully, but these errors were encountered: