Again on 100% cpu

[Marco Martin]

On Wednesday 16 November 2011, Sebastian Trüg wrote:
> sadly this does not help since the status() calls indicate that nothing
> is happening.
> 
> As for the initial startup: this could be the ontology import. On
> devices you could think of shipping a default configuration which
> already comes with a pre-filled database.
> 
> Initial cpu hogging which is independent of the first run is something I
> already have plans for.
> 

is there some other way to debug what's happening there?

-- 
Marco Martin