-
Notifications
You must be signed in to change notification settings - Fork 233
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
Poor performance on Linux #2239
Comments
#661 might be related. I'll try the fixes proposed there but I can only confirm a duplicate once I make another video call (probably tomorrow). |
I have applied the fix proposed in #661, namely to define the environment variable |
Hi @hmenke, do I see correctly that you have ~4 GB of memory? |
@ffflorian Yes, I have 4GB of physical memory and 10GB of swap. However, memory doesn't seem to be the problem, especially after applying the fix from #661 which improved idle performance of Wire a lot! Is there a way to profile Wire to see where it is spending the most time? Is there something like a compiler switch like |
Not as far as I know, that would be a thing for Electron to implement. Also please note that the Linux executable is still experimental. |
I'm having an issue where leaving it running for a long period (1-2 days) will take up most of my mem and CPU (up to 12 gb of memory). I'll provide some more details next time I leave it running - looks similar to the performance problems you're having. |
Electron (or rather V8) comes with a profiler. One can dump profiling data by starting Wire with
This will generate a couple of Source: https://v8.dev/docs/profile |
Thanks @hmenke, I was not aware of that. |
I have extracted the profiling from my recent Wire call. All the logs can be found below. Unfortunately, I don't know which one of these is the main process, but I think it is isolate-0x384b37dac000-v8.txt. In there I see something which is a bit worrying:
It looks like Wire is performing an enormous amount of I/O, because this generates two orders of magnitude more ticks than any other operation. isolate-0x289ef7cf2000-v8.txt |
Okay, to get only a single log file you have to launch Wire with
This will create a single
|
Even without a video call, Wire idles at 35 % CPU usage. That'd probably be okay on a really old CPU, but a Core i5 isn't that old. And it eats 5.8 GiB of my 8 GiB of RAM. Again, this is just having the application running in the background seemingly not doing much. Even running several virtual machine takes less ressources. o.O Do we have at least a workaround since there is no fix yet? |
I tried to modify LoadingSpinner to just return The spinner is rendered when the account is visible:
which it always is when it's selected I assume so it's always rendered. |
@charlag I think I love you. Wire team, please take note that if you devote just a few resources into performance improvements it is way better for the userbase than fancy features that 1% of the users will use. 100% of the users will enjoy longer battery life and more available CPU. |
Since 2022.09.20.08.41 (or 3.28.2946) Wire does not hang anymore when pasting an image into the input field. I don't know what you've changed but before I always had to wait up to 20-30 seconds (depending on the image size) until the desktop client was responsive again after pasting an screenshot. Now I can paste images within one seconds which is nice. Thanks! |
It was indeed massively reduced with #5164 Sorry that it took so long! |
Wire version: 3.6.2885 (latest from
deb https://wire-app.wire.com/linux/debian stable main
)Wire for web version: -
Operating system: Debian GNU/Linux 9.8 (stretch) Linux 4.19.0-0.bpo.2-amd64
Which antivirus software do you have installed: -
What steps will reproduce the problem?
wire-desktop
What is the expected result?
Reasonable CPU and RAM usage.
What is the actual result?
Enormous CPU and RAM usage to an extent where the system becomes unresponsive and the frame rate of the video call drops to about 2 FPS.
Please provide any additional information below.
Screenshot of
htop
while I'm in the video call.The text was updated successfully, but these errors were encountered: