-
-
Notifications
You must be signed in to change notification settings - Fork 188
import in 1.0.0 seems to be lot slower than 0.6.x #65
Comments
Ref #65 First shot as today gives ``` ❯ node benchmarks.js customProperties takes 0.20704s calc takes 0.03314s customMedia takes 0.01792s mediaQueriesRange takes 0.00871s customSelectors takes 0.00889s colorRebeccapurple takes 0.07094s colorHwb takes 0.07437s colorGray takes 0.09796s colorHexAlpha takes 0.07138s colorFunction takes 0.11102s fontVariant takes 0.00786s filter takes 0.08778s rem takes 0.01469s autoprefixer takes 1.04424s ``
@magsout result before 1.0 (cssnext 0.6.6)
after 1.0
|
I just added a simple
autoprefixer seems responsible :/ @ai any idea ? |
Yeap, Autoprefixer has too difficult logic inside. I canceled many issues, because they will make Autoprefixer slower, but anyway we have too many checks and look backs. But I will start optimization process. BTW, anyway Autoprefixer is the fastest prefix solution right now :D. |
Task about optimization: postcss/autoprefixer#406 |
My previous bench was buggy. Here is a more relevant
So autoprefixer is not that slow @ai. My bad. @magsout I not really sure about how you can get slow result like that. Do you have a lot of import ? |
@magsout maybe you have a looots of import and a lot or url() references ? |
I make some tests with 0.6.6 and got stuff like that
Result seems to be the same. Note that import is not a feature anymore in v1.0 (it's an option). Like url. So I think I might be one of this 2, probably url option since it's new. If you inline, it might be the reason. Both import & url option use fs sync :/ (no choice for now). |
I think anyway Autoprefixer speed up will be nice. |
Always :) |
I tried on my MBA (yesterday I tried on another machine) version
version
Edit: I forget to add admin.css |
If I runned only on If I runned only on And yes, I have lot of import in that file. |
Here are the tests I made:
gulp-cssnext : 0.6.0 - features: false gulp-cssnext : 0.6.0 - features: true gulp-cssnext : 1.0.0 - features: false gulp-cssnext : 1.0.0 - features: true No No |
@MoOx tell me if my tests are enough, of if you need anything else |
Can you try with url to false too ? |
with gulp-cssnext : 1.0.0 - features: false - url : false gulp-cssnext : 1.0.0 - features: false - url : true No No |
So it clearly seems related to a postcss-import change. We need to take a deeper look into that. |
Cannot reproduce with the private data you send me @magsout. |
seems ok now |
@magsout reported to me that we got a x7 times.
I need to take a look to that.
Edit: not that much :)
The text was updated successfully, but these errors were encountered: