Godot 3.6 beta: Opening big project from 3.5 causes editor to be slow until godot cache is cleared

[Marigem]

Tested versions

3.6 beta 5

System information

Arch Linux

Issue description

Editor was painfully slow on 3.6, meanwhile it was working fine and was responsive on 3.5 (Same project).

Clearing all Godot cache solved the issue. Hopefully this will help if someone runs into the same situation.

I don't know what exactly caused it.

Steps to reproduce

N/A

Minimal reproduction project (MRP)

N/A

[Calinou]

Clearing all Godot cache solved the issue. Hopefully this will help if someone runs into the same situation.

By clearing Godot cache, do you mean removing the cache folder listed in File paths in Godot projects?

[Marigem]

Clearing all Godot cache solved the issue. Hopefully this will help if someone runs into the same situation.

By clearing Godot cache, do you mean removing the cache folder listed in File paths in Godot projects?

Yes, I deleted everything in ~/.cache/godot/
And in ~/.config/godot/projects/MyProjectName

Though I'm not sure which one fixed the issue.

[PabloDevGit]

What are the implications of doing that?
I mean, if I do that, will it bring about any changes in my project? in addition to the increase in speed.

Will absolutely nothing happen and the project will simply go smoother or faster?

[Marigem]

What are the implications of doing that? I mean, if I do that, will it bring about any changes in my project? in addition to the increase in speed.

Will absolutely nothing happen and the project will simply go smoother or faster?

Always use git. If you are worried about something making changes to your project, not only can you see if something changed in the project but you can also revert the unwanted changes if you use git.

But in this instance as long as you don't touch your actual project directory, your project will remain completely unchanged. These cache folders is where the godot editor remembers what scene you had opened last, where the editor camera was looking, which tabs you had un-collapsed in the inspector for a selected node, stuff like that.

Although clearing the cache doesn't guarantee a speed increase. I had absolutely no problems on 3.5 but in this instance the editor was unbearably slow on 3.6 on this particular project, for whatever reason, until I cleared the cache and now it's as snappy as it is on 3.5.

[lawnjelly]

I foolishly deleted my ~/.cache/godot/ and ~/.config/godot/projects/MyProjectName but didn't notice any difference. I should have profiled beforehand though just in case. But I'm going to profile in a sec to see if anything shows up.

I did have a massive amount of files in the cache though, something like 26,000, and it's possible that just accessing these is slowing things down, although I don't know why this might be different in 3.5 and 3.6 (I'm not personally aware of any PRs that changed this but there might be some).

@Marigem are you using a hard disk by any chance rather than SSD? That might be a lot slower for file accesses, to the extent that the rest of us don't notice.

File access might not be as good on windows, but you are using linux (as am I).

UPDATE:
Ah on profiling the editor I'm seeing a little bit of:

EditorFileSystem::_scan_fs_changes()
EditosFileSystem::_test_for_reimport()

And I've not seen those before in profiling. I'll see if I can work out from the history if anyone has altered these.

@Marigem it would be helpful to know which version of 3.5 you have confirmed the problem didn't occur with, just in case any PRs have been cherry picked to 3.5 and I can discount them.

Did it occur the same with opening a small project as it does with opening the project that causes the issue? It would help to know whether it is project specific.

[Marigem]

I'm using an SSD, and the difference was huge. For example adding items to an array in the inspector took like 1 second for each item to be added, when I selected a node it took about 1 sec for the inspector to update with my selection.

After clearing the cache it went back to normal as it was in 3.5 and the editor responds immediately to my actions.

Before that I was using the latest 3.5.3 which can be downloaded on the website. My own build of 3.6 and the latest official 3.6 beta had the same problem, I tried creating a brand new project but it didn't have that problem, only the one project did.

I checked right now and other small older projects don't have that problem.

[lawnjelly]

Does the problem still occur at all (now you have deleted the caches)?

It would be nice if you could help bisect by trying the earlier betas to find where the problem first started occurring, but maybe it is not possible now.

I'll try profiling 3.5.3 to see if I can notice anything different jumping out from the profiles that is using more CPU.

[Marigem]

It would be nice if you could help bisect by trying the earlier betas to find where the problem first started occurring, but maybe it is not possible now.

I don't think it's possible now as well. I've been using 3.6 with my project since then and I haven't encountered the problem after that.