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

Input lag on HiDPI 4K when maximizing window #4110

Open
clamydo opened this issue Aug 7, 2023 · 4 comments
Open

Input lag on HiDPI 4K when maximizing window #4110

clamydo opened this issue Aug 7, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@clamydo
Copy link

clamydo commented Aug 7, 2023

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

Windows 10

WezTerm version

20230712-072601-f4abf8fd

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

I experience a noticeable input lag (up to estimated 500 ms) proportional to the size of the window and of the screen resolution (when I move a window between displays of different resolutions). This is true for both WebGPU and OpenGL mode. The performance on Dx12 is much better than with Vulkan backend.

However, it feels to me, in fullscreen (without decorator) the lag is smaller again even on 4K resolution.

I am on a Intel(R) Core(TM) i7-8565U CPU with integrated Intel GPU. Is it too weak?

I tried the current nightly (20230712-072601-f4abf8fd), but it crashed when resizing the window.

On my, admittedly substantially beefier, Linux machine I have no issues.

To Reproduce

Open a new window, type, observe lag between pressing key and appearance of the character on the screen.

Configuration

config.front_end = "WebGpu"
config.webgpu_power_preference = "HighPerformance"
config.webgpu_preferred_adapter = {
	backend = "Dx12",
	device = 16032,
	device_type = "IntegratedGpu",
	name = "Intel(R) UHD Graphics 620",
	vendor = 32902,
}

Expected Behavior

No (noticable) input lag, even on slightly dated laptop hardware.

Logs

Debug Overlay
wezterm version: 20230712-072601-f4abf8fd x86_64-pc-windows-msvc
Window Environment: Windows
WebGPU: name=Intel(R) UHD Graphics 620, device_type=IntegratedGpu, backend=Dx12, vendor=32902, device=16032
Enter lua statements or expressions and hit Enter.
Press ESC or CTRL-D to exit

Anything else?

Thx for making Wezterm. I ❤️ it!

@clamydo clamydo added the bug Something isn't working label Aug 7, 2023
@wez
Copy link
Owner

wez commented Aug 7, 2023

FWIW, the resize crash is from the upstream wgpu crate:

@wez
Copy link
Owner

wez commented Aug 7, 2023

Can you clarify what you mean by 500ms of input lag? Are you saying that every key press takes 500ms to render?
Only in certain applications? Is it that bad in the debug overlay itself?

@wez wez added the waiting-on-op Waiting for more information from the original poster label Aug 7, 2023
@clamydo
Copy link
Author

clamydo commented Aug 8, 2023

Are you saying that every key press takes 500ms to render?

Exactly. The time between key press and rendering.

Update: I've tried to measure it with the slomo mode of my camera, which puts it more in the 200+-50 ms ballpark for maximised window and 100 ms for full screen.

Only in certain applications? Is it that bad in the debug overlay itself?

Independent of applications and shells (in WSL2!) and also in the debug overlay.

@github-actions github-actions bot removed the waiting-on-op Waiting for more information from the original poster label Aug 8, 2023
@MartenBE
Copy link

MartenBE commented Nov 5, 2024

I am also having this issue on Fedora 41 KDE with wezterm 20241104_083404_51c794ac. Maximizing the window on 4K screen really increases the CPU usage used by wezterm and it becomes slow to respond. Resize it to a smaller window and cpu usage and lag also scale down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants