http://vhanda.in/blog/2012/08/faster-nepomuk-queries/
Сначала создадим 100500 сервисов, а потом обратно их начнём объединять. Это прорыв!
If you ignore file handling in Nepomuk, we have two main services -
- Storage Service
- Query Service.
The Storage Service is responsible for managing the ontologies, initializing virtuoso, and other data management functions. The QueryService exists for caching queries and running them in a separate thread.
Now the Query Service obviously need to access the virtuoso database, and for that it needs to go through the storage service. This communication happens through a local socket. The same socket which all other applications use to access Nepomuk.
Last week, I finally merged the query service into the storage service.
I was aiming for a small memory decrease, and a slight performance upgrade on the queries. Boy, was I wrong! The additional local socket seems to have been a huge bottleneck.
