[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
| | Andre Poenitz <[EMAIL PROTECTED]> writes:
>>
| | | On Thu, Oct 16, 2003 at 11:07:52AM +0200, Lars Gullik Bjønnes wrote:
>>>> This is some results without the textcache removed.
>>>>
>>>> time ./src/lyx -x 'lyx-quit'
>>>>
>>>> real 0m0.313s
>>>> user 0m0.150s
>>>> sys 0m0.050s
>>>>
>>>>
>>>> time ./src/lyx -x 'command-sequence file-open ../lyxdoc/UserGuide1.lyx
>>>> ; lyx-quit ;'
>>>>
>>>> real 0m1.439s
>>>> user 0m0.770s
>>>> sys 0m0.040s
>>>>
>>>>
>>>> Actually buffer switching feels very fast, but I cannot really
>>>> understand where we have got the speed from. Any explanations?
>>>
| | | Not really. Rebreaking should be a bit faster nowadays, but this
| | | exceeds my expectations.
>>
| | I have a feeling that something fishy is going on. Should the "no text
| | in cache" message from BufferView::Pimpl::resizeCurrentBuffer() be
| | emitted on every buffer switch? Why isn't it?
>>
| | Are there some hidden caching going on?
>
| Or is it just the debugstream not working...
| (and why is it not working... I wonder...)
(somehow debugstream is not workign with gcc 3.4 with maximum
optimization, I will investigate.)
I'd really like to know, how slow does a computer need to be before
the buffer switch get unbearably slow. So some tests on P-III's and
P-II's would be nice (slower than that I do not care too much about.)
--
Lgb
