Extremely slow and laggy performance comparing to default terminal
Discord username (optional)
No response
Describe the bug
I am experiencing performance issues with the Warp terminal when running it on a remote server with the latest version of Kali Linux using the GNOME environment. The Warp terminal appears to be slow and laggy compared to a normal terminal in this setup.
To reproduce
Steps to Reproduce:
Set up a remote server running the latest version of Kali Linux with the GNOME desktop environment installed. Install and open the Warp terminal on the remote server. Execute various commands within the Warp terminal and observe the response time and overall performance. Compare the performance with the standard GNOME terminal by executing similar commands.
Expected behavior
Expected Result: The Warp terminal should function with comparable efficiency and responsiveness as the standard GNOME terminal.
Actual Result: The Warp terminal exhibits slower response times and a general lack of smoothness in operation, significantly impacting usability.
Frequency: This issue occurs consistently every time the Warp terminal is used in the described environment.
Screenshots
Operating system
Linux
Operating system and version
Lastest Kali linux ( kernel Linux 6.6.9-amd64 )
Shell Version
zsh 5.9 (x86_64-debian-linux-gnu)
Current Warp version
v0.2024.04.23.08.01.stable_03
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
warp-terminal_0.2024.04.02.08.02.stable.01_amd64.deb
Additional context
i had the version 0.2024.04.02.08.02.stable.01 on older similar setup and it was working fine.
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Hi @coder3119, thanks for reporting this case. Can you elaborate how you're connected to this remote server, e.g. is it VNC, RDP, X11 forwarding over SSH?
Looking at #4864, it seems that this may not be limited to remote Linux sessions.
@coder3119 Thank you for flagging. A few questions for you:
- Did this specifically stop working with the
v0.2024.04.23.08.01.stable_03release? Could you test on the following versions to see if it still reproduces?
v0.2024.04.16.08.02.stable_00: https://releases.warp.dev/stable/v0.2024.04.16.08.02.stable_00/warp-terminal_0.2024.04.16.08.02.stable.00_amd64.debv0.2024.04.09.08.01.stable_01: https://releases.warp.dev/stable/v0.2024.04.09.08.01.stable_01/warp-terminal_0.2024.04.09.08.01.stable.01_amd64.debv0.2024.04.02.08.02.stable_01: https://releases.warp.dev/stable/v0.2024.04.02.08.02.stable_01/warp-terminal_0.2024.04.02.08.02.stable.01_amd64.deb
- Does this still reproduce if you disable "Completions while typing"?
I'm using VMware Remote Console (VMRC) but the same behavior when i use RDP. when i switched to using Xfce, I noticed a slightly improvement
@coder3119 We believe we just pushed a fix for this in the latest version of Warp (v0.2024.04.30.08.02.stable_02). Would you mind updating and confirming it fixes things for you?
We've gotten feedback from a number of users that the input lag was, in fact, fixed in v0.2024.04.30.08.02.stable_02, so I'm going to close this out as fixed.
If you're still seeing the input lag regression on that version, please re-open.
For anyone with an input delay or performance issue who finds this issue in the future, please open a new issue.
Fixed a bug! Please ignore the devx bot.
I was experiencing the same issue on Debian Testing, Warp version v0.2024.09.03.08.02.stable_03. My OS was running on Wayland. However, changing to X11 solved the problem and Warp is launching pretty fast now :-)
Hi, thank you so much for addressing this issue in the latest release (v0.2024.09.17.08.02.stable_01) . I updated my installation, but it seems it is not fixed. It still takes ages to open Warp on Wayland. With X11 the app opens within 1-2 seconds.
After upgrading to Ubuntu 24.10, warp take an extremely amount of time to launch rendering it unusable
Hi @tothpsk and @ifedan-ed. Could you both provide your Warp logs + a video demonstrating the behavior so we can debug further? Thank you! https://docs.warp.dev/help/sending-us-feedback#gathering-warp-logs
Hi @alokedesai, here are the videos and logs:
launching Warp on X11: https://github.com/user-attachments/assets/3859e9bf-650f-451a-ba36-0ee28d848a92 launching Warp on Wayland: https://github.com/user-attachments/assets/80f45483-6296-44ab-a20a-77e040e7371e logs: warp-terminal.zip
Hope this helps finding the cause of the issue. Best wishes,
Peter
facing the same issue on v0.2024.12.10.15.55.stable_03 WSL 2
facing the same issue on v0.2025.01.08.02.stable_04 running on WSL2. The device I'm on has no dedicated graphics card and the CPU is constantly getting maxed out by VmmemWSL (in this case warp terminal). The integrated graphics seem to take the hit in performance causing the CPU to slow down to a crawl if wsl has GPU support enabled, if gpu support is not enables it simply wont open.
I am having the same issue running Wrap on my desktop Ubuntu 24.04.1 LTS. It does not feel snappy to type. (The video provided is a bit slower than normal cause I was recording.)
https://github.com/user-attachments/assets/ea7de3af-0a5c-4cd1-882b-8d2d15945f7f
It's April 2025 and Warp Terminal is still extremely slow for Windows. :(
@sewandev Can you describe the performance issues you're seeing on the Windows? Would you be free to join a meeting with us to dig into the issues further? We'd be happy to give you a gift (warp swag or a gift card) as a thank you for your time.
@alokedesai
zprof
num calls time self name
-----------------------------------------------------------------------------------
1) 1 31797.15 31797.15 57.49% 30254.19 30254.19 54.70% warp_bootstrapped
2) 1 19343.16 19343.16 34.97% 11220.63 11220.63 20.29% warp_precmd
3) 5 10442.50 2088.50 18.88% 10442.50 2088.50 18.88% warp_send_json_message
It's becoming unusable
slow for me on windows too.
@GurdipS5 What issues are you seeing on Windows? Would you mind filing a new issue with more details and tagging me on it?
Lento tambien en linux debian, consumo de prosesador y al escribir tarda en mostrar, hasta que se arregle continuo con alacritty
It probably depends on login method. When I login using email and link, it works great. When I use login using Google account, it is laggy like hell.
@Isolator79 What OS are you on? Could you send me a video of the exact behavior you're seeing when you login with Google vs email so I can debug further? Thanks!
My email is [email protected]
It probably depends on login method. When I login using email and link, it works great. When I use login using Google account, it is laggy like hell.
I have logged in using email and password it lags for me anyway
For anyone experiencing this issue, it would be very helpful to post the following to to help facilitate debugging:
- What OS you're on
- Your warp logs
Thank you!
This will probably not help you, but for the record for everyone else stumbling across this issue: I've experienced this issue on Windows and disabling the integrated GPU usage (Warp Settings -> Features -> System -> Prefer rendering new windows with integrated GPU) fixed this issue for me.
This will probably not help you, but for the record for everyone else stumbling across this issue: I've experienced this issue on Windows and disabling the integrated GPU usage (Warp Settings -> Features -> System -> Prefer rendering new windows with integrated GPU) fixed this issue for me.
this fixed the lag in my case, thanks!
This will probably not help you, but for the record for everyone else stumbling across this issue: I've experienced this issue on Windows and disabling the integrated GPU usage (Warp Settings -> Features -> System -> Prefer rendering new windows with integrated GPU) fixed this issue for me.
Thanks! 👍
Warp team, please look into this issue - Warp on Windows is still almost unusable from lag. I have tried all tips above and from Discord, but it does not help.
As long as Warp is the foreground window, the whole Windows OS is laggy, and especially Warp is extremely laggy. If I focus another window, it takes a second and then the lag disappear. Focusing Warp again and the lag is immediately back.
What has been tried:
- Disable “Prefer rendering new windows with integrated GPU (low power)” in Settings > Features > System. This resolved input lag/stutter for multiple users. [Input lag; Extremely slow].
- Switch Preferred graphics backend to DirectX 12 (then restart Warp). Some issues were fixed by moving off Vulkan. [Performance issues]
- Force Warp to use the discrete GPU via Windows Graphics Settings or your GPU control panel. [Warp opens once; Performance issues]
- On NVIDIA, set “Preferred refresh rate” to “Highest available” for warp.exe in NVIDIA Control Panel. This fixed heavy FPS drops for some. [Poor performance]. I also tried setting Low Latency Mode to Ultra, Vertical Sync to Off and Power Management Mode to max.
- If Warp won’t honor backend selection or still lags, try setting WGPU_BACKEND=dx12 as a user env var, then restart. [Not launching]. I also tried WGPU_POWER_PREF=high. Other WGPU apps have no issue on my system.
- Tested minimize Warp or move it to a different monitor—some users see lag only when Warp is focused or on a specific display. [Poor performance]
- Tested setting CPU affinity to only 3D-cores or only non-3D cores on my 7950X3D CPU
- Tested changing refresh rate on displays from 144 to 60.
Windows 11, RTX 4090, Ryzen 7950X3D.
Still same problem on debian.