[Kde-pim] Review Request: Disable contact searching in message viewer

[Vishesh Handa]

On Thu, Oct 25, 2012 at 11:39 AM, Andras Mantia <amantia at kde.org> wrote:

> Anders Lund wrote:
>
> > But if the problems stays, will someone work on them? It's been like this
> > for a long time now, and the issues in this request is just a few of a
> > myriad of problems between akonadi and nepomuk.
>

I don't think any of the Nepomuk developers have ever looked at the pim
code. I'm starting to run PIM full time now, even though I still don't use
kmail, akonadi is at least running. So I am starting to face some of the
problems you have.

I'll try to fix whatever I can.


> Vishesh, the nepomuk developer promised to look at the contact search
> problem. But that will affect only 4.10, as 4.10 uses Nepomuk2, while 4.9
> Nepomuk1.
> So I suggest to keep the workaround in 4.9.
>
> BTW, here is a bug report about it:
> https://bugs.kde.org/show_bug.cgi?id=288364
>

Just to keep you updated. I've pushed the optimized versions of contact
search job queries to master. Please let me know if you still encounter
performance problems with it.

Because of the nature of the ontologies (read db schema in Nepomuk) the
queries are slightly complex. If performance is still a problem, then the
ontologies will have to be changed. The Nepomuk Ontology people won't like
it, but we don't have a choice. This would be the last option. Ideally, we
should run it through a profiler and see if virtuoso is actually the
bottleneck.


>
> > Today is one of those days where I seem to have to shut down akonadi if I
> > need to use my pc. Only, some of the stuff I want to do is answer mails
> > and use my calendar...
> >
> > I have spent hours waiting for a window where I can do that during the
> > day.
> >
> > Often, while nepomuk/virtuoso-t is running wild, I can not find any
> > running jobs in akonadiconsole. But as soon as I shut down akonadi (or at
> > least after a few minutes) neopmuk and virtuoso-t cools down, and things
> > becomes normal.
>
> You can also debug somewhat what causes the Nepomuk slowdown. Here are some
> tips:
>
> http://techbase.kde.org/Projects/Nepomuk/VirtuosoInternal#Common_Commands
>
> The status() method in the virtuoso command line is the interesting when
> things slow down to find out the query that causes the slowdown.
>

Right now there are 2 main problems that I know of -

1. Email Indexing - It's very slow. Christian and I are looking into it,
but you'll have to give me some time. The hard feature freeze is in a week,
and I still have to finish a couple of features. This clearly counts as a
bug fix, so I can always work on it.

I will try and optimize it as much as I can before 4.10 releases.

2. Nepomuk Queries via QueryService - Due to certain things in the nepomuk
internal query engine, there were some complicated joins being added to
each query. I've pushed a fix for this in nepomuk-core on Monday. It should
help a lot. Unfortunately, it required a lot of changes in nepomuk and I
would not be comfortable backporting them.


>
> Andras
> _______________________________________________
> KDE PIM mailing list kde-pim at kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> KDE PIM home page at http://pim.kde.org/
>



-- 
Vishesh Handa
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/