Hi all,
about the SuSE X.Org 6.8.2 RC3 RPMs and compose cache:
- SuSE specific changes since RC2:
[...]
- added compose cache (details for testing will follow)
The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory
$HOME/.compose-cache
, writable only by you. The next X application will create a compose cache entry in this directory which will be used in the future. Compose cache entries expire once a day. Changes in the compose tables are tracked and caches invalidated automatically.
Future releases will have a global compose cache, so a .compose-cache directory will only be needed for caching if you have your own compose table. In the meantime, please create the directory for testing and report all compose- and deadkey-related issues.
Thanks
Matthias
On Wednesday 26 January 2005 07:19, Matthias Hopf wrote: <snip>
The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory
$HOME/.compose-cache
<snip>
I've created the .compose-cache but I guess I'm not sure what exactly it does. Does anyone know? Which apps are currently utilizing this? I only see two small cache files (>1MB) in the folder and I don't exactly understand what's being cached.
On Sunday 13 February 2005 1:27 pm, Jake Sallee wrote:
On Wednesday 26 January 2005 07:19, Matthias Hopf wrote:
<snip>
The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory
$HOME/.compose-cache
<snip>
I've created the .compose-cache but I guess I'm not sure what exactly it does. Does anyone know? Which apps are currently utilizing this? I only see two small cache files (>1MB) in the folder and I don't exactly understand what's being cached.
I would also like to understand what exactly is being cached and how it is affecting performance.
I also get warnings such as following when I start any X-based program
Ignoring broken XimCache /home/oshogg/.XCompose
Any idea what this means? Is .XCompose supposed to be a file or directory? what should it contain?
thanks
On Mon, Feb 14, 2005 at 06:52:08AM -0800, Osho GG wrote:
On Sunday 13 February 2005 1:27 pm, Jake Sallee wrote:
On Wednesday 26 January 2005 07:19, Matthias Hopf wrote:
<snip>
The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory
$HOME/.compose-cache
<snip>
I've created the .compose-cache but I guess I'm not sure what exactly it does. Does anyone know? Which apps are currently utilizing this? I only see two small cache files (>1MB) in the folder and I don't exactly understand what's being cached.
I would also like to understand what exactly is being cached and how it is affecting performance.
I also get warnings such as following when I start any X-based program
Ignoring broken XimCache /home/oshogg/.XCompose
Any idea what this means? Is .XCompose supposed to be a file or directory? what should it contain?
Matthias knows the details. He is currently on LWE in Boston and will answer when he's back next week.
Stefan
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------
On Monday 14 February 2005 6:57 am, Stefan Dirsch wrote:
On Mon, Feb 14, 2005 at 06:52:08AM -0800, Osho GG wrote:
On Sunday 13 February 2005 1:27 pm, Jake Sallee wrote:
On Wednesday 26 January 2005 07:19, Matthias Hopf wrote:
<snip>
The compose cache accelerates program startup times and memory consumption considerably, especially for UTF8 locales. In order to use the compose cache, please create a directory
$HOME/.compose-cache
<snip>
I've created the .compose-cache but I guess I'm not sure what exactly it does. Does anyone know? Which apps are currently utilizing this? I only see two small cache files (>1MB) in the folder and I don't exactly understand what's being cached.
I would also like to understand what exactly is being cached and how it is affecting performance.
I also get warnings such as following when I start any X-based program
Ignoring broken XimCache /home/oshogg/.XCompose
Any idea what this means? Is .XCompose supposed to be a file or directory? what should it contain?
Matthias knows the details. He is currently on LWE in Boston and will answer when he's back next week.
Thanks, I found some useful information at
http://wiki.kde.org/tiki-index.php?page=Performance%20Tips
under the section Key composing (XIM)
Stefan
Public Key available
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany
I've created the .compose-cache but I guess I'm not sure what exactly it does. Does anyone know? Which apps are currently utilizing this? I only see two small cache files (>1MB) in the folder and I don't exactly understand what's being cached.
libX11 now caches the compose tables. These are typically large for UTF8 locales. Compose tables are used for DeadKeys (like '`~ on European keyboard layouts) and for the Compose mechanism (most users don't even know it exists). But the tables had to be parsed for each X application on startup time.
I would also like to understand what exactly is being cached and how it is affecting performance.
Approx. 40-200ms decreased startup time for every X application, depending on your processor. Approx. 240KB saved memory per X application.
These numbers are only valid for UTF8 locales. They would be much smaller for other locales or personal (small) .XCompose files.
I also get warnings such as following when I start any X-based program Ignoring broken XimCache /home/oshogg/.XCompose
Wow. That might be a bug. Can you mail me your .XCompose file and a 'ls -al ~/.compose-cache'?
There should be an easy fix for that, but I'd like to know what happens here. You should be able to nuke this message by just moving all files from ~/.compose-cache to a different location (for later examination).
Any idea what this means? Is .XCompose supposed to be a file or directory? what should it contain?
That comment implies to me that you did not create this file by intention. Hm. That's strange...
You'll find a typical compose file e.g. in /usr/lib/X11/locale/en_US.UTF-8/Compose
Though personal compose files would be *much* smaller...
Thanks
Matthias
-
Jake Sallee -
Matthias Hopf -
Osho GG -
Stefan Dirsch