Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-20 Thread Milian Wolff
On Tuesday 20 January 2015 04:32:21 Kevin Kofler wrote: Milian Wolff wrote: It can, indeed. But funnily enough it's not going to be much faster, at least in the tests I did. Still, one should probably be doing this anyways. I'll try to dig up my patch for that and sent it to Gerrit. It's

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Milian Wolff
On Monday 19 January 2015 20:48:54 Olivier Goffart wrote: On Monday 19 January 2015 20:15:22 Milian Wolff wrote: Hello all, when I run my heaptrack [1] tool on Qt 5 applications, I often stumble upon the compose TableGenerator. It initializes many QStrings and also consumes ruoghly

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Kevin Kofler
Milian Wolff wrote: It can, indeed. But funnily enough it's not going to be much faster, at least in the tests I did. Still, one should probably be doing this anyways. I'll try to dig up my patch for that and sent it to Gerrit. It's a pity that one cannot just convert a const char* to a QChar

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Thiago Macieira
On Monday 19 January 2015 20:15:22 Milian Wolff wrote: I usually don't use the compose key, so my naive assumption would be that lazy-loading this table would help the common case of startup quite a bit already. Or is this required for other things that I don't expect? It applies to dead

[Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Milian Wolff
Hello all, when I run my heaptrack [1] tool on Qt 5 applications, I often stumble upon the compose TableGenerator. It initializes many QStrings and also consumes ruoghly 400KB of memory. I wonder whether we could optimize this somehow? The best approach of course would be to have a OpenDesktop

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Olivier Goffart
On Monday 19 January 2015 20:15:22 Milian Wolff wrote: Hello all, when I run my heaptrack [1] tool on Qt 5 applications, I often stumble upon the compose TableGenerator. It initializes many QStrings and also consumes ruoghly 400KB of memory. I wonder whether we could optimize this somehow?

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Paeglis Gatis
-project.org development-bounces+gatis.paeglis=theqtcompany@qt-project.org on behalf of Thiago Macieira thiago.macie...@intel.com Sent: Monday, January 19, 2015 9:38 PM To: development@qt-project.org Subject: Re: [Development] optimizing QComposeInputContext / TableGenerator? On Monday 19 January

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Thiago Macieira
On Monday 19 January 2015 21:17:00 Giuseppe D'Angelo wrote: The best approach of course would be to have a OpenDesktop standard that allows mmapping the compose table in and using it from there. Probably not feasible. Why not? x...@freedesktop.org. I think I can easily convince the EFL

Re: [Development] optimizing QComposeInputContext / TableGenerator?

2015-01-19 Thread Giuseppe D'Angelo
Il 19/01/2015 20:15, Milian Wolff ha scritto: The best approach of course would be to have a OpenDesktop standard that allows mmapping the compose table in and using it from there. Probably not feasible. Why not? Also cf. https://codereview.qt-project.org/#/c/74524/