Skip to content
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

fix: upgrade tinyglobby #121

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SuperchupuDev
Copy link

@SuperchupuDev SuperchupuDev commented Nov 5, 2024

fixes #119

the problem with glob usage in this project is that globSync is called multiple times which isn't optimal, as it forces tinyglobby to traverse the filesystem multiple times. in theory, globSync could be called just once during the walking process, but that would be a bigger refactor, although a possible one

EDIT: this pr upgrades tinyglobby, ignore the text below this

it looks like under a default config most patterns passed to globSync aren't even globs, so this PR avoids unnecessary globSync calls when none of the patterns are globs

screenshot of patterns passed to tinyglobby in 6.1.0, each log is a different glob call

image

locally (windows) this change makes it faster than 5.15.0, with the reproduction from #119 taking 25s in 5.15.0 and 13s in latest with the change (latest without the change took too long to measure)

@SuperchupuDev
Copy link
Author

ci is failing, will debug tomorrow

@robertsLando
Copy link
Member

robertsLando commented Nov 5, 2024

Could you also test if there are improvements with the test-80-compression-node-opcua test? It actually takes 5 min on ubuntu to complete.

Seems now it went down to 2min: https://github.com/yao-pkg/pkg/actions/runs/11675697212/job/32510712730?pr=121#step:7:20 :) I think there is still range of improvement here. Could you try enabling that test also for windows and mac?

Just remove this lines:

// FIXME: this test takes a long time to run (from 5min on linux up to 10 minuntes on windows)
// run only on linux to save time on CI
if (process.platform !== 'linux') {
return;
}

@robertsLando robertsLando changed the title avoid globbing non-dynamic paths fix: avoid globbing non-dynamic paths Nov 6, 2024
@robertsLando
Copy link
Member

I also created #122, I would like to compare performances of tests in this two PR

@SuperchupuDev
Copy link
Author

from my local tests in the zip repro of #119 this should be faster than #122, since the unnecesary glob calls were still present back then

@robertsLando
Copy link
Member

In fact seems this is faster 👍🏼

lib/walker.ts Outdated Show resolved Hide resolved
@SuperchupuDev
Copy link
Author

okay i see why at least some tests fail, it's due to this project using directory expansion, which means that globbing dir is the same as globbing dir/**. dir itself is technically not dynamic so it gets skipped which shouldn't happen

@robertsLando
Copy link
Member

@SuperchupuDev Yep understood, could you fix that?

@SuperchupuDev
Copy link
Author

trying

@SuperchupuDev
Copy link
Author

SuperchupuDev commented Nov 6, 2024

okay, fixing it would just make all patterns dynamic, making performance not change whatsoever. we need a better solution. there needs to be a refactor in the walker logic so that all patterns are pushed into an array and then when all of them are collected call globSync once

@robertsLando
Copy link
Member

@SuperchupuDev Makes sense, agreee

@robertsLando
Copy link
Member

@SuperchupuDev News on this?

@SuperchupuDev
Copy link
Author

SuperchupuDev commented Nov 20, 2024

been busy with university, i have to debug and figure out why vite's tests fail with tinyglobby's upcoming version (which should fix the perf issue), could try today

@SuperchupuDev SuperchupuDev changed the title fix: avoid globbing non-dynamic paths fix: upgrade tinyglobby Nov 28, 2024
@SuperchupuDev SuperchupuDev marked this pull request as draft November 28, 2024 13:41
@SuperchupuDev
Copy link
Author

@robertsLando changed this pr to the upcoming tinyglobby version instead, can you compare performance again?

@SuperchupuDev
Copy link
Author

SuperchupuDev commented Nov 28, 2024

okay, thanks. fyi it's 4 minutes on fast-glob as well: https://github.com/yao-pkg/pkg/actions/runs/11703987586/job/32595478258?pr=122#step:7:20

@SuperchupuDev
Copy link
Author

SuperchupuDev commented Nov 28, 2024

although this pr should solve the perf issue reported in #119, for the record, if you want to avoid unnecesary globbing one solution can be setting expandDirectories to false in tinyglobby's options, then doing what this pr did before i force pushed. it'd be a breaking change though as users would have to replace some of their patterns i.e. src with src/**

@robertsLando
Copy link
Member

Ok thanks for that! I would not go for that option as I think there will be too much edge cases to handle and I'm quite sure it could cause some unexpected issues I don't want to deal with right now. We can merge this if it's ready 👍🏼

@robertsLando robertsLando marked this pull request as ready for review November 28, 2024 16:55
@robertsLando
Copy link
Member

I correct myself: we can merge this once you have a release for tinyglobby :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Slow packaging of pnpm workspaces project
2 participants