Why is there one completion thread per completion model?

Esben Mose Hansen kde at mosehansen.dk
Mon Sep 27 13:17:00 UTC 2010

On Monday 27 September 2010 14:00:03 Milian Wolff wrote:
> Couldn't it be one thread for all? Or is this too complicated and having
> lots  of threads no issue?

One issue is obviously big backtraces :)

Threads in itself causes very little overhead; however if each thread checks 
something at each keystroke it certainly adds up. 

Kind regards, Esben

More information about the KDevelop-devel mailing list