-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance improvement - magepack bundle to utilize multiple cores #113
Comments
If anyone has any ideas for the implementation please share. |
Not sure about multiple cores, but I'm assuming the slowest part is accessing the webpages and waiting for everything to load so it can extract the appropriate javascript. So running those tasks in parallel/async would see the biggest performance improvement, but not sure how to go about implementing that reliably. And of course, the faster your website is, the faster it will finish collecting |
@Quazz magepack bundle is not doing any requests, its working with already generated static content, or I am wrong? |
@kanevbg No, you're right; it's magepack generate that does the requests. |
@drabikowy do you know if this will be picked up for implementation from creativestyle, can you forward it to someone for consideration? |
Please someone from creativestyle/magesuite share tough for implementation before I go ahead and code it for a PR. |
One word please? |
Up |
1 similar comment
Up |
In one of my projects it takes 5 minutes to bundle the static content (
magepack bundle
).1 theme with 17 locales.
The text was updated successfully, but these errors were encountered: