Again on 100% cpu

[Sebastian Trüg]

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.

Cheers,
Sebastian

On 11/16/2011 02:27 PM, Marco Martin wrote:
> Hi all,
> 
> this is another of those 100% cpu reports :/
> 
> this is what happens at the moment in plasma active, probably reproduceable 
> elsewhere as well.
> 
> on the first run when .kde doesn't exists, virtuoso stays at 100% cpu for some 
> minutes.
> this could be almost expected, but randomly happens on subsequent startups as 
> well: virtuoso at 100 for some minutes, then all starts to work well when the 
> usage goes down again.
> 
> attached there is some status() from isql, one during the first run and the 
> other two from a subsequent run, done in several seconds of distance, in the 
> same run.
> 
> what seems strange is that there does not seem to be any query running and 
> taking long time, so is not really clear what is doing during those minutes.
> 
> any idea? and any idea on how some more informations could be gathered?
> 
> 
> Cheers,
> Marco Martin
> 
> 
> 
> _______________________________________________
> Active mailing list
> Active at kde.org
> https://mail.kde.org/mailman/listinfo/active