<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Severe performance degradation on a macOS with a 5K display" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137468#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Severe performance degradation on a macOS with a 5K display" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137468">bug 137468</a> from <a class="email" href="mailto:ilford@gmail.com" title="Leo Wang <ilford@gmail.com>"> Leo Wang</a> <pre>(In reply to Tor Lillqvist from <a href="show_bug.cgi?id=137468#c7">comment #7</a>) > Leo, do you have any way to objectively measure the impact of these patches, > out do you just estimate by eyeball? (or is the difference so very obvious > if one just knows what kind of document to use and what to do while editing > it?) > > I submitted the first patch on your behalf as > <a href="https://gerrit.libreoffice.org/c/core/+/104476">https://gerrit.libreoffice.org/c/core/+/104476</a> . With iStat Menus' CPU/GPU dropdown menu: Original: 5-7 fps (almost unusable) Patched: 12-18 fps (acceptable, but not smooth) when the content is pure text. Quartz Debug also gives the FPS number, but since it updates the dock icon frequently, the number is usually much higher than the actual, especially when the FPS is very low. I am still trying to find where the pixel format conversions are introduced. AquaSalGraphics::copyArea and AquaSalGraphics::copyBits are the hottest spots, they call CGContextDrawLayerInRect and CGContextDrawLayerAtPoint and those 2 functions call argb32_image_mark then rgba32_sample_rgba32 is called.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>