While debugging into issue 98052 I noticed that a lot of cycles in that use case (first keypress in empty 
Writer) are completely wasted by framework::KeyMapping objects. Since the implementation of that 
class only seems to deal with constant data rebuilding the key<->name maps shouldn't be done each 
time. Also the query methods in that class should be const-ified, as they don't change the KeyMapping 
object. Maybe the class should be pImpled and the const pImpl-entation should be reused.

Especially the method XCUBasedAcceleratorConfiguration::impl_ts_load() seems to be infamous for 
constructing/destructing the currently expensive KeyMapping object over and over. In the use case 
mentioned above (first keypress in Writer) this was done 5460 times!!!

Here is a simple patch to reduce the thousands of invocations to one by reusing the (to-be const) 
object:
--- a/framework/source/accelerators/acceleratorconfiguration.cxx
+++ b/framework/source/accelerators/acceleratorconfiguration.cxx
@@ -1287,1 +1287,1 @@ void XCUBasedAcceleratorConfiguration::impl_ts_load( sal_Bool bPreferred, 
const
-            KeyMapping aKeyMapping;
+            static KeyMapping aKeyMapping;