On 09/08/2010 10:43 AM, Pavel Sanda wrote:
Richard Heck wrote:
If so, I think we could restore the call when needed. The question would be
when it breaks. But, as I say in the FIXME, it's hard to see how the macros
need updating if the buffer doesn't.
i dont use macros myself so its j
On Tue, Sep 7, 2010 at 6:48 PM, Pavel Sanda wrote:
> e.g. go to section 7.2.1 of additional lyx manual, having outliner
> uncollapsed.
> even typing is slower than displaying, not to speak about cursor movement
> which
> is just impossible.
>
> looking at top i see most of cpu usage is taken ins
Richard Heck wrote:
> If so, I think we could restore the call when needed. The question would be
> when it breaks. But, as I say in the FIXME, it's hard to see how the macros
> need updating if the buffer doesn't.
i dont use macros myself so its just guessing, but when i leave macro inset
by th
On 09/08/2010 09:19 AM, Pavel Sanda wrote:
Richard Heck wrote:
I don't really understand this either, but it certainly look as if the
updateMacros() calls are eating a lot of time. Just on general grounds, we
need to call it only when we must. There is surely no need to call
updateMacros jus
Abdelrazak Younes wrote:
>
> Maybe the outliner triggers a resize event? That could kill the performance
> indeed...
no its not triggered.
pavel
Richard Heck wrote:
> I just had a quick look at this. I think we should try commenting out the
> line:
> buffer_.updateMacros();
fyi i tried to kill this line and its still deadly slow. the bottleneck must be
somewhere inside Qt/X.
pavel
On 09/08/2010 03:40 PM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
forgot to add - i went in the middle of additional manual, switched on the
outliner and just hold right arrow key for two paragraphs...
Note that gprof does not show you X usage, only what happens inside LyX
(not
Jean-Marc Lasgouttes wrote:
>> forgot to add - i went in the middle of additional manual, switched on the
>> outliner and just hold right arrow key for two paragraphs...
>
> Note that gprof does not show you X usage, only what happens inside LyX
> (not even Qt). It is better to compile a release b
Le 08/09/2010 14:46, Pavel Sanda a écrit :
Pavel Sanda wrote:
i tried to make profile. the output is gigantic and don't fully understand the
output right now...
http://195.113.26.193/~sanda/junk/gprof.txt
(9mb)
forgot to add - i went in the middle of additional manual, switched on the
outline
Pavel Sanda wrote:
i made shorter summary from the flat part of the profile, ie cumulative time
spent inside the functions, subcalls included; cut below 5%:
with ouliner:
[1] 87.80.002.54 722 lyx::dispatch(lyx::FuncRequest
const&) [1]
[2] 87.80.002.54 722
On 09/08/2010 03:19 PM, Pavel Sanda wrote:
Richard Heck wrote:
FIXME there when working on updateBuffer(). This is the ONLY call to this
routine that is neither (a) inside the read and export routines nor (b)
inside updateBuffer(). That will sharply limit the number of calls to
updateMacros(
Richard Heck wrote:
> I don't really understand this either, but it certainly look as if the
> updateMacros() calls are eating a lot of time. Just on general grounds, we
> need to call it only when we must. There is surely no need to call
> updateMacros just when you are moving the cursor.
>
> I
On 09/08/2010 08:46 AM, Pavel Sanda wrote:
Pavel Sanda wrote:
i tried to make profile. the output is gigantic and don't fully understand the
output right now...
http://195.113.26.193/~sanda/junk/gprof.txt
(9mb)
forgot to add - i went in the middle of additional manual, switched on th
Pavel Sanda wrote:
> now i want to create second profiling output when outliner is off...
http://195.113.26.193/~sanda/junk/gprof_nooutliner.txt
> pavel
Abdelrazak Younes wrote:
> On 09/08/2010 02:46 PM, Pavel Sanda wrote:
>> Pavel Sanda wrote:
>>
>>> i tried to make profile. the output is gigantic and don't fully
>>> understand the output right now...
>>> http://195.113.26.193/~sanda/junk/gprof.txt
>>> (9mb)
>>>
>> forgot to add - i wen
On 09/08/2010 02:46 PM, Pavel Sanda wrote:
Pavel Sanda wrote:
i tried to make profile. the output is gigantic and don't fully understand the
output right now...
http://195.113.26.193/~sanda/junk/gprof.txt
(9mb)
forgot to add - i went in the middle of additional manual, switched on th
Pavel Sanda wrote:
> i tried to make profile. the output is gigantic and don't fully understand
> the output right now...
> http://195.113.26.193/~sanda/junk/gprof.txt
> (9mb)
forgot to add - i went in the middle of additional manual, switched on the
outliner and just hold right arrow key for two
Abdelrazak Younes wrote:
> Please make some profiling before attacking this or this field. Threads are
> nice but must be used with care.
i tried to make profile. the output is gigantic and don't fully understand the
output right now...
http://195.113.26.193/~sanda/junk/gprof.txt
(9mb)
pavel
Abdelrazak Younes wrote:
> Maybe this is somewhat related.
>
> http://blog.martin-graesslin.com/blog/2010/09/driver-dilemma-in-kde-workspaces-4-5/
so i upgraded everything from kernel to xorg and the drivers around to the
newest packages and except that google earth became unusable flashing circus
On 09/08/2010 02:10 AM, Abdelrazak Younes wrote:
On 09/07/2010 05:48 PM, Pavel Sanda wrote:
hi,
while typing some docs into our manuals i must admit that lyx editing
performance
when outliner is simultaneously opened is really horrible.
e.g. go to section 7.2.1 of additional lyx manual, havi
Abdelrazak Younes wrote:
> Here with Linux/Qt4.7/gcc4.4.3/KDE4.5 compiled with
>
> -O3 -DNDEBUG (cmake release option), there no issue. Everything's very
> fast.
>
> When typing really fast, Xorg takes 30% cpu and lyx2.0 takes 22%. I have a
> Core2 Duo centrino @ 2GHz.
thanks for the response. t
On 09/07/2010 05:48 PM, Pavel Sanda wrote:
hi,
while typing some docs into our manuals i must admit that lyx editing
performance
when outliner is simultaneously opened is really horrible.
e.g. go to section 7.2.1 of additional lyx manual, having outliner uncollapsed.
even typing is slower tha
Stephan Witt wrote:
> Hm... don't know if this are good or a bad news...
rather good news. lets wait on some other report from linux arch.
pavel
Am 07.09.2010 um 17:48 schrieb Pavel Sanda:
> hi,
>
> while typing some docs into our manuals i must admit that lyx editing
> performance
> when outliner is simultaneously opened is really horrible.
>
> e.g. go to section 7.2.1 of additional lyx manual, having outliner
> uncollapsed.
> even ty
hi,
while typing some docs into our manuals i must admit that lyx editing
performance
when outliner is simultaneously opened is really horrible.
e.g. go to section 7.2.1 of additional lyx manual, having outliner uncollapsed.
even typing is slower than displaying, not to speak about cursor moveme
25 matches
Mail list logo
