Bug 218302

Summary: Persistent code browser database
Product: [Applications] kdevelop Reporter: Mihai <mihai.stanescu>
Component: generalAssignee: kdevelop-bugs-null
Status: RESOLVED NOT A BUG    
Severity: wishlist CC: david.nolden.kde, vkrevs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mihai 2009-12-11 17:23:21 UTC 
Version:           3.9.96 (using KDevPlatform 0.9.96) (using 4.3.3 (KDE 4.3.3), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.29-gentoo-r5


Use some sort of persistent storage for code browser database to speed up loading when opening a project (parse only changed files)

Right now code browser parses every time and i work on something like 86MB of source code which is parsed in a few minutes.

I almost never parse whole project because takes too long and if kdevelop crashes its bye bye database anyway.
Comment 1 Milian Wolff 2009-12-11 17:27:51 UTC 
We already use a persistent storage. The problem is that crashes can make this storage invalid and hence it has to be cleared. The more stable kdevelop becomes, the less you'll have to reparse.
Comment 2 Vadym Krevs 2009-12-12 00:23:09 UTC 
Strictly speaking, kdevelop could have used something like Berkely DB to avoid db corruption in such situations ...
Comment 3 David Nolden 2009-12-12 00:58:43 UTC 
@Vadym Krevs: That doesn't make sense, given the amount of information we store in the duchain, any kind of 'stable' database storage would be horribly slow, and also complete overkill, as the information is not 'valuable' at all, it's just a cache.

Just keep reporting your crashes, then KDevelop will become more stable, and the database won't be cleared that often. Parsing performance is worked on as well.