Closed richb-hanover closed 1 year ago
56GB is extreme!
Unfortunately I think this is because of both cargo and https://github.com/PRQL/prql/issues/1836, and there's no particularly easy way to solve it. But:
Thanks for these thoughts. It doesn't seem there's much to do about rebuilding right now. I can live with it.
re: size of target
: I read that reddit thread, and I'm thinking that a simple workaround is rm -rf target
Obviously, I'd rebuild the whole thing, but it would save a lot of brain power over learning to use cargo clean
or cargo-sweep
...
@max-sixty , @eitsupi Sorry for necro-posting - please let me know if this is the same thing we discussed back in May...
I recently removed all containers, images, and volumes from Docker, and rm -rf prql/target
I then rebuilt the entire Dev Container, and already have a 25GByte target folder. I see multiple builds of many files (see ls
below).
In particular, I see multiple builds of _liblibduckdbsys and prqlc (and many others), separated in time by a few minutes or hours.
It feels to me as if these builds are not being cached. Is this the same cause as earlier? Should I create a separate issue? What other information could I provide? Thanks as always.
Expand the "Details" to see the ls -lhS prql/target
I'm not sure what's going on here. This might be more of a cargo problem than a PRQL problem, although we're keen to help with anything that facilitates your PRQL work.
Does running cargo clean
solve the issue for a couple months? Or how quickly is it accumulating?
What happened?
Every time I quit VS Code, re-launch it, then run
task run-book
, the Dev Container rebuilds a lot of stuff. This happens even if no changes have been made to the source files. This takes a couple minutes on my fairly modern Macbook, so it's annoying. (It's OK if I ^C the command and re-run. No rebuild is necessary until I quit VS Code.)BUT... the size of the target/debug/deps directory continually increases. At the moment it occupies 56 GB (!) on my computer. When I look at the contents of the folder, I see a large number of ~250MByte
mdbook_prql-24440258aa393249
files with dating back to March. (See below.) In fact, each item in the "Compiling" list above generates one of those files).My questions:
Many thanks
PRQL input
SQL output
Expected SQL output
MVCE confirmation
Anything else?
No response