Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Aim is very slow since 3.12.0
See original GitHub issue🐛 Bug
I observed a huge slow down when using Aim since updating to 3.12.0. I did not have this issue with previous 3.11.2.
Launching aim up takes a bit less than 1 minute.
Creating a run tracker through Python with aim.Run is very long (1 to 2 minutes).
Aim UI is very slow, for instance I cannot go to the Images tab, it keeps loading and then my browser tab crashes saying “Something went wrong”.
I tried on both SSD and HDD.
To reproduce
- Install Aim 3.12.0 or greater.
- Track metrics and images in the code.
- Launch Aim UI with
aim up. - Launch the code.
Expected behavior
Starting Aim UI with aim up shouldn’t take that long, and Aim UI itself shouldn’t make my browser crash.
Environment
- Aim Version: >=3.12.0
- Python version: tested on both 3.8.13 and 3.10.7
- pip version: 22.2.2
- OS: Ubuntu
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:22 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey @Aonnghus! We are on the way to completely re-design the locking mechanism in Aim. The fix for the performance issue related to locks will be shipped along. We target to release the new version at the end of next week.
Got it. Thanks! We’ll include this change in the
v3.14.0as well, as a workaround for now. In the meanwhile we’ll try to improve the filesystem identification mechanism, as clearlyFileLocks can be used for a case that you’ve described, but we still opt to useSoftFileLocks.