[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 218261] Kdevelop is unusable (too slow) when project is stored
From:       David Nolden <david.nolden.kde () art-master ! de>
Date:       2009-12-12 0:03:52
Message-ID: 20091212000352.8704B2B8EE () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=218261


David Nolden <david.nolden.kde@art-master.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.nolden.kde@art-master
                   |                            |.de




--- Comment #4 from David Nolden <david nolden kde art-master de>  2009-12-12 01:03:51 ---
Whenever reparsing a file, kdevelop has to check whether any of its hundreds of
includes has changed. And if it decides to reparse a file, then it has to
search for all "#include"ed files within all include-paths.

Both of these are probably the reason why it is so slow on your remote
filesystem. There is not much that can be done here, as both of these steps are
required. The filesystem could do some caching to speed it up.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]