On Sun, Nov 11, 2007 at 05:25:20PM +0100, Tommaso Cucinotta wrote: > Andre Poenitz ha scritto: >> An entirely unscientific test (sitting in front of the computer and >> counting) yields ~4s for loading the UserGuide before applying the patch >> and ~13s afterwards. There is some additional debug output, but I don't >> think the resulting scrolling in the terminal accounts for all of those >> nine extra seconds. >> >> So please: Produce some numbers showing that there are no inacceptable >> regressions wrt to performance. A performance degradation by a factor of >> 3 for loading documents does not look like a good start. >> > Well, I'm verifying on my laptop. But I want to be sure to have > two LyX compiled exactly with the same options, and debug > disabled. On my laptop ([EMAIL PROTECTED]), it takes ~30min. a full > recompilation of LyX, so I guess I'll have numbers within one > hour or so (and I'm also deleting a couple of kernel source > trees to accomodate for the needed space). > > Anyway, please note that, with the current patch, *all* par > metrics and heights are pre-computed on a document load > (full metrics are discarded for all pars but the visible ones), > so I expect anycase a slow-down on document opening.
Some performance decrease for loading will be acceptable... > As already mentioned on the list, I'd like to switch to an > incremental computation of the document height that is > made in the background while the user is already able to > work on the document. > I'd make such change as a further incremental patch, but if > you prefer the all-in-one approach, I can go further to such > step. "Incremental" is fine if the direction is ok and each step leaves us with a usable code base. Andre'
