duchain cache directories

[Milian Wolff]

On Donnerstag, 10. November 2016 13:33:37 CET René J.V. Bertin wrote:
> Hi,
> 
> Am I right that the kdevduchain caches are saved per session and not per
> project? That means that if you add a project to multiple sessions, you end
> up with multiple copies of the parser cache, which are probably redundant
> because they reflect the project and not the session in which it is opened?
> 
> Since someone is currently looking into related things, might I suggest to
> consider reorganising this cache so that duplicates are avoided if that is
> not the case at the moment?
> 
> And out of curiosity, wouldn't it be better (in whatever way) to use a
> database (sqlite3 for instance) rather than the current approach using
> plenty of individual files? Or would that lead to overhead and issues for
> which akonadi has become infamous?

The cache is not cross-process safe, thus it must be per-session.

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20161120/f47c96b7/attachment.sig>