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

windows binaries hanging/slow due to many files in PATH #791

Open
simonmichael opened this Issue May 30, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@simonmichael
Owner

simonmichael commented May 30, 2018

The windows binaries on the download page appear to hang at startup (eg hledger --version) on a windows 10 machine with some symbolic links present in %PATH%. A fresh dev build does not hang. I suspect the binaries (and stack-ghc8[02].yaml) need to be updated with a newer version of the directory lib which fixes this issue. This is currently blocked on appveyor build issues (the latest looks like commercialhaskell/stack#3950).

simonmichael added a commit that referenced this issue May 30, 2018

@simonmichael simonmichael changed the title from windows binaries hanging due to symlinks ? to windows binaries hanging/slow due to many files in PATH May 30, 2018

@simonmichael

This comment has been minimized.

Owner

simonmichael commented May 30, 2018

The directory upgrade didn't help. Instead it was caused by "a very large amount of small text log files in \WINDOWS\System32".

It appeared that a newer build made with ghc 8.4 did not have the issue. Perhaps the newer base or directory packages made windows filesystem operations more efficient ?

Currently the windows binaries are built with ghc 8.2 to avoid
haskell/network#313 /
commercialhaskell/stack#3944 /
commercialhaskell/stack#4346 .

Actions:

  • switch the binaries to ghc 8.4 asap (when a workaround arrives for the above)
  • ideally, reproduce the issue, or at least mimic it on unix, and confirm/clarify the ghc 8.4 fix
  • look for efficiency gains in the addon-detecting code in Hledger.Cli.CliOptions

simonmichael added a commit that referenced this issue May 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment