Re: [Tracker] Clues regarding improving performance of tracker-store



On 12 July 2013 18:52, Ivan Frade <ivan frade gmail com> wrote:
Hi!

 If you are not using email, that ontology will be translated into some
tables in the database but they are never touched. It should not make big
difference.

Aha, this is very good to know. It should mean I can keep several
flattened ontologies side-by-side them impacting each other
negatively. This is good!

Do you think slimming down the ontologies could yield a performance
boost for the store?


 If you are using Tracker in some specific environment, maybe you could
simplify the ontology removing hierarchies and using specific classes for
your use cases. Those would be private changes (not to commit in master).

Yes, I wouldn't want to screw up your ontologies, no worries ;) As a
side note however.. Wouldn't it be nice to have several sets of
ontologies available for the Tracker users to pick from? I think
Philip touched on the subject of letting applications supply their own
ontologies. Currently though, it sounds like it would be possible to
simply swap the ontology definitions completely, and thereby provide
new functionality this way. Perhaps the Tracker project is not the
right place to gather such sets of ontologies however, since they
would be incompatible with each other?

Is there support for altering the ontologies? I have seen
.ontology-files. It seems to me that these are the place to go.

The wording of [1] seems to indicate that there are more places in
Tracker where ontologies can be modified other than the .ontology
files. Am I reading this correctly, or are all ontology
related-matters handled through the .ontology files?


 All ontology definitions are in those .ontology files and nowhere else.
When Tracker starts, it reads those files, and if they have changed updates
the database schema.

Thanks for clearing this up for me. Again, this is good news! :)

--
Regards,
Jonatan Pålsson

Pelagicore AB
Ekelundsgatan 4, 6th floor, SE-411 18 Gothenburg, Sweden


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]