forked from enlightenment/efl
Carsten Haitzler
d16809d648
so i've been wondering what is going on for a few days... and i've figured it out finally... my mouse seems ot like to generate 1000 events per second. not your usual 100 or 200. it only happened on this one machine so i was wondering what on earth was up. this machine was different in other ways like an arm cpu, differing gpu (rx550), different distro and so on. this is creating a storm of motion events.. and this is causing all sorts of overhead in just trying to deal with them all like generate more internal events, emit signals for every one of them and so on. there is no attempt to play catch-up or anything - just build up a bigger and bigger queue of them to deal with. this is NOT GOOD. this restores our old commented out event skipper that got commented out during some xcb work actually - not on its own. it was a huge xcb patch that commented it out. this restores it and makes it a little cleaner with a bool and now the perf issues i was seeing are gone. this is such a major performance fix that this deserves a backport. @fix @optimize |
||
---|---|---|
.. | ||
Ecore_X.h | ||
Ecore_X_Atoms.h | ||
Ecore_X_Cursor.h | ||
ecore_x.c | ||
ecore_x_atoms.c | ||
ecore_x_atoms_decl.h | ||
ecore_x_composite.c | ||
ecore_x_cursor.c | ||
ecore_x_damage.c | ||
ecore_x_dnd.c | ||
ecore_x_dpms.c | ||
ecore_x_drawable.c | ||
ecore_x_e.c | ||
ecore_x_error.c | ||
ecore_x_events.c | ||
ecore_x_fixes.c | ||
ecore_x_gc.c | ||
ecore_x_gesture.c | ||
ecore_x_icccm.c | ||
ecore_x_image.c | ||
ecore_x_keygrab.c | ||
ecore_x_mwm.c | ||
ecore_x_netwm.c | ||
ecore_x_pixmap.c | ||
ecore_x_present.c | ||
ecore_x_private.h | ||
ecore_x_randr.c | ||
ecore_x_region.c | ||
ecore_x_screensaver.c | ||
ecore_x_selection.c | ||
ecore_x_sync.c | ||
ecore_x_test.c | ||
ecore_x_vsync.c | ||
ecore_x_window.c | ||
ecore_x_window_prop.c | ||
ecore_x_window_shape.c | ||
ecore_x_xi2.c | ||
ecore_x_xinerama.c | ||
meson.build |