I checked that the gconf patch does not have a measurable performance impact by
measuring the time of
GNOME startup (press enter in gdm until panel menu works).
cold cache:
- upstream gconf, per-lang tree: 76.7 s 75.5 s 75.0 s
- patched gconf, per-lang tree: 77.1 s 74.8 s 74.9 s
hot cache:
- upstream gconf, per-lang tree: 28.0 s 28.1 s 28.1 s
- patched gconf, per-lang tree: 28.0 s 28.3 s 28.1 s
In theory, with a completely converted *.schemas tree, startup time
should be faster, since gconfd-2 does not have to load and parse all the
translated xml files any more. Getting descriptions is a relatively
seldom operation and not needed at all for startup. If an application
needs translations of its own gconf keys, its .mo file should already be
loaded, thus the performance impact for this should be negligible.
The only real performance impact that will probably happen is with
gconf-editor, where you need lots of translations for many different
keys. But first I don't expect this to actually be noticeable by users,
and second this is well worth paying this price in exchange for the
general space and time savings.
** Changed in: gconf2 (Ubuntu)
Status: In Progress => Fix Committed
--
stop shipping static gconf translations, use gettext at runtime
https://bugs.launchpad.net/bugs/123025
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf2 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
