Again on 100% cpu

[Sebastian Trüg]

On 11/16/2011 03:30 PM, Marco Martin wrote:
> 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?

hm, apart from looking at the code I would not know at the moment. I
suspect a lot of small queries...