unexpected background thread after Revise 1.13.1

[dpinol]

After Revise 1.13.1, due to #987, loading the package causes a background thread to run for a long time. This impacts my performance benchmarks even though I don't explicitly load Revise (it's loaded by JET).
Would you consider a PR adding an env var to disable loading the cache?

thanks

[aviatesk]

I'm fine with adding a Preferences.jl configuration entry for that.

[dpinol]

I'm fine with adding a Preferences.jl configuration entry for that.

Done #992 thanks

[schillic]

I also see that recently the Julia process takes up a full core when starting with Revise active. But for me this takes several minutes, making it really annoying to develop at the moment.

Thanks for providing a fix. Please release it when you have time.

Also, I think the user experience is much worse with the new default. So it would be better to invert the behavior to an opt-in: load the cache only if the preference is switched on.

[axsk]

I realized this issue for the first time after updating from 3.12 -> 3.13.1.
As I am bound to 1 thread only (since PyCall seems to be broken on multithreaded julia these days), so the REPL became unresponsive for quite a while after loading Revise.
This caused me to give up on using the beloved Revise for a while...
I just tried 3.13.0, but here Revise just takes long (30+ secs) to load, so I downgraded to 3.12 for now.
I hope I don't have to stay there forever :)

[dhanak]

Same here, I have Revise fixed to version 3.12 for now, because with 3.13, the background thread is spinning for minutes on each start. And what I get in exchange is a dubious and rarely necessary benefit, of which I would opt out without hesitation.

#1008 will be the remedy for this. Let's hope it makes into a release soon.

[lassepe]

The situation should be much improved on the current master. The current master is not tagged as a new version because it makes struct revision opt in, so it would be breaking. There are a few PRs still pending on the Julia side to fully fix this performance issue.