-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
superslow using
when active project is on high latency network
#38813
Comments
Output of https://docs.microsoft.com/en-us/sysinternals/downloads/procmon with entries that touch the remote share looks like this
Using a snippet
outputs for the number of
To summarize, when calling |
How big are the tomls? could we just read them all into memmory once and keep them until |
In this demo case, Project.toml is two lines, Manifest.toml is 98 lines. Just what ones gets from starting a new project and |
Try with nightly, it should be improved there (the result get cached). |
Problems with nightly #38838 |
Same behavior with latest nightly
Simple file read
If I filter the procmon logfile from
i.e., environment files are only read once (or twice). But filtering for
As a bonus, I think this is a competitive entry to the TTFP contest 😀 with
When the activated environment is on the local disk,
|
Can you try with this branch: https://github.com/JuliaLang/julia/tree/kc/assume_unchanged_loading |
No practical improvement
|
Hm, I thought that would remove the stat calls. Is the procmon log the same? |
Procmon log says that
[This is in a different machine than above, but numbers are of the same order.] |
Ping time to the share server is about 195 ms. The slowness is not specific to CSV.jl.
With the default
C:\Users\jaakkor2\.julia\environments\v1.6\Project.toml
,using
is reasonableContents of the
\\my\share\Project.toml
is onlyJust reading the toml files is not dominating the time.
Version info, but same slowness occurs with Julia v1.5.3.
Next step is to have a look with https://docs.microsoft.com/en-us/sysinternals/downloads/procmon as was done in #36911.
The text was updated successfully, but these errors were encountered: