[SOLVED] Chromium terrible performance after 3 seconds from start

kekc · 2017-11-12 18:08:48

In my adventurous campaign I moved from dummy > intel > modesetting driver and now face another super-strange hurdle: chromium.

For some reason it becomes superslow after 3 seconds from start - each keypress lags for like 3-4 seconds and only then shows up on the screen. But:
- It performs flawlessly in the beginning - I can even type in quickly and load some page
- Firefox works normally

What I did:
- Symptoms look quite similar to this: https://bbs.archlinux.org/viewtopic.php?id=220766. However, deleting everything from ~/.config/chromium did not help.
- I reinstalled chromium several times (pacman -Rsn)
- I reinstalled mesa and lib32-mesa, removed xf86-video-intel
- Starting chromium from shell does not show anything except typical warning about some env variable
- Nothing in syslog
- Same behavior in LXDE and XFCE
- Tried all the tips and tricks from arch-wiki pages for Chromium

What I didn't try but will:
- Chromium-dev (currently building, yawn)
- Chrome

Any ideas what else to try / what can cause this?

Last edited by kekc (2017-11-13 08:28:58)

lo1 · 2017-11-12 18:39:57

Have you tried disabling your extensions / using chromium with its default configuration?

Last edited by lo1 (2017-11-12 18:40:06)

kekc · 2017-11-12 19:21:34

Yes, it's a fresh install - no extensions / addins, default config.

Last edited by kekc (2017-11-12 19:21:53)

kekc · 2017-11-12 21:47:29

Okay, the cause is indeed the GPU and probably drivers:
- Chrome behaves exactly the same
- If run with "--disable-gpu" switch - everything works fine. Not sure it is enough to mark the thread as SOLVED though, as it means no hardware acceleration in chromium under modesetting.

GPU performance is clearly screwed:

$ glxinfo | grep -i render
direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 6000 (Broadwell GT3)
    GL_ARB_compute_shader, GL_ARB_conditional_render_inverted,
    GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp,
    GL_ARB_compute_shader, GL_ARB_conditional_render_inverted,
    GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent,
    GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,

$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
1087 frames in 5.1 seconds = 214.248 FPS
6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS

Any thoughts on how to troubleshoot this further?

Last edited by kekc (2017-11-12 22:02:25)

seth · 2017-11-12 23:13:46

https://wiki.archlinux.org/index.php/In … 28VSYNC.29 ?

kekc · 2017-11-13 08:24:47

It worked! Thanks, Seth. How did you know?!
I mean I'm feeling dumb - the answer was in wiki all along, but I did not have a slightest clue that it could be relevant to my case.
Shall we put some symptoms to wiki?

Last edited by kekc (2017-11-13 08:27:17)

seth · 2017-11-13 08:39:43

This didn't look very random ....

6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
6 frames in 6.0 seconds =  1.000 FPS
5 frames in 5.0 seconds =  1.000 FPS
...

This would belong into some "how to create a headless xvnc wiki", I assume - don't know anything about the wiki rules, but you could log your endeavor at least somewhere (and then move that into the arch wiki if appropriate)

kekc · 2017-11-13 10:20:09

Anyway, thanks for pointing out! I amended the wiki article by putting symptoms.

Arch Linux

#1 2017-11-12 18:08:48

[SOLVED] Chromium terrible performance after 3 seconds from start

#2 2017-11-12 18:39:57

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#3 2017-11-12 19:21:34

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#4 2017-11-12 21:47:29

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#5 2017-11-12 23:13:46

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#6 2017-11-13 08:24:47

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#7 2017-11-13 08:39:43

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

#8 2017-11-13 10:20:09

Re: [SOLVED] Chromium terrible performance after 3 seconds from start

Board footer