Skip to content
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

Startup and tex-replacement performance fixes #18296

Merged
merged 3 commits into from
Oct 3, 2023
Merged

Startup and tex-replacement performance fixes #18296

merged 3 commits into from
Oct 3, 2023

Conversation

hrydgard
Copy link
Owner

@hrydgard hrydgard commented Oct 3, 2023

The Vulkan-in-other-process check was slower than necessary by using shell APIs early in startup, which cost a couple hundred ms to load. Let's avoid that.

I found this while profiling for another problem, which was that texture replacement decimation tries to lock textures, and we ended up blocking the main thread unnecessarily while large textures were loaded, leading to less performance glitches when using texture packs.

@hrydgard hrydgard added the Performance Unexpected slow performance issues label Oct 3, 2023
@hrydgard hrydgard added this to the v1.17.0 milestone Oct 3, 2023
@hrydgard hrydgard merged commit 7a2f308 into master Oct 3, 2023
18 checks passed
@hrydgard hrydgard deleted the startup-perf branch October 3, 2023 11:06
// (this is an external process.)
bool result = VulkanMayBeAvailable();

LogManager::Shutdown();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, not even starting up the log manager. Might be safer not to call these things in case they start crashing in certain cases later when init never happened.

-[Unknown]

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, yeah, I got a little aggressive here - wanted the spawned process to be as pure a VK check as possible, and missed this path. I'll clean it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Performance Unexpected slow performance issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants