> fvwm stays barely usable when the application generates 20.000.000 > ...NAME... PropertyNotify events (machine with four cores). The > X server blocks one cpu at 100%, fvwm uses 50% to 60% on another > core, and the application uses about 12% on a third. This looks > pretty good to me - as long as fvwm is twice as fast as the X > server it cannot be the bottleneck. >
ha!... if you can survive 20M spam events, you just might the most resilient WM out there! > Do you notice any change in performance when starting maple? Is > fvwm more responsive or less? I have not been able to reproduce the problem from before since running the fvwm version from a few days ago. Maple seems completely usable no matter what worksheets I throw at it... I can't tell any obvious differences - when it loads correctly, it works just fine. > (The first time maple freaks out > responsiveness may be not very good; I think that is caused by the > X server or Xlib allocating lots of memory for the events; on a > second go fvwm stays usable for me.) > Since the version from a few days ago, when it loads, all cores are doing stuff for a couple of seconds... but then once loaded all is good. I've tried tripping it by say "manually" flooding the WM with events by switching desktops, loading new windows, etc... but it's been working ok. > The code ist still hardly tested and experimental and may cause > any number of bugs. > > I'll play with it for a while, and report anything unusual. thanks for all your work!! peter
