>As a data point, I don't see any slowdown in Linux, using latest
>branch and Qt 4.4.3, under Fedora 8. UNLESS I open the View Source
>window, when (unsurprisingly) I do. Same result if I put the files
>on a network drive.
>
>Is it possible that LaTeX is being generated, even though the window
>isn't shown?
>

I don't think LaTeX code generation is the problem. All reports are
speaking about a master document with childs. Usually the LaTeX code is
then nothing else than a few includes and maybe a title, toc, references
and so.

Don't you believe my reasoning about the thousands file accesses per
second ?

Anyway, a possible reason why it is worse at windows are the following
lines of code:

FileName.cpp:
937   FileName const lhs(os::internal_path(l.absFilename())); 
938     FileName const rhs(os::internal_path(r.absFilename())); 

In os_win32.cpp::get_long_path the function GetLongPathName is called.
This function checks whether the file exists. (And then we do it again
in the constructor of FileName).

So, if there are four filesystem-checks in Linux, there are at least six
on Windows and maybe the compiler does something smart when
os::internal_path does nothing.

And now some speculation: I'm using UNC-paths. That has caused problems
in the past I believe. Maybe the fi.exists() function somehow returns
false, or we use a wrong representation of the path somewhere. If then,
caching is turned on in FileName(), then the problem gets worse again.

By the way, can you remember what problem Bennet had which made you
adding the lhs.refresh() and rhs.refresh() lines to
FileName::operator==(). This solution looks a bit like "Abdel's hammer".


>Richard

Vincent

Reply via email to