Hey Vishesh,
Thank you for your answer, there is no problem to store triples within
Sesame, but to add the index via SesameSail.
Regarding Virtuoso, it seems only OWLIM-SE and OWLIM-Enterprise support
full-text search, but they are not for free, thus we are not interested.
Thank you,
Sorin
Am 16.05.2013 12:06, schrieb Vishesh Handa:
Hey Sorin
On Wed, May 15, 2013 at 12:19 PM, Sorin Gheoghiu
<[email protected]
<mailto:[email protected]>> wrote:
Hello Nepomuk,
we are interested to use SesameSail but we encountered an issue.
We sent yesterday an email to sesame discusssion list while we
seek help to optimize it, but it seems the product is not further
developed, although I noticed a newer LuceneSail version has been
updated 10 months (https://github.com/kreuzverweis/lucene-sail-3.0).
Can you please confirm wheather the product is actively maintaned
or not? If yes we are glad to work with you, otherwise we have to
seek for alternatives.
This mailing list is for the nepomuk-kde project, which is not
affiliated with DFKI.
About 4 years back we did try to use Sesame, but we eventually moved
to OpenLink's virtuoso[1] in order to store triples. It has worked
quite well, and can easily store 10 million triples.
[1] http://virtuoso.openlinksw.com/
Thanks and regards,
Sorin
-------- Original-Nachricht --------
Betreff: Re: [Sesame] Huge memory use during LuceneSail load
Datum: Wed, 15 May 2013 15:09:51 +1200
Von: Jeen Broekstra <[email protected]>
<mailto:[email protected]>
Antwort an: Sesame discussion list
<[email protected]>
<mailto:[email protected]>
An: [email protected]
<mailto:[email protected]>
On 15/05/13 05:59, Sorin Gheoghiu wrote:
> Hi,
>
> Our goal was to import around 10 milions triples using LuceneSail. We
> have Sesame 2.6.9, lucene-core 2.6.9 and lucenesail 2.1.0. We've
> expected that a lot of memory is needed, but what we experienced it was
> beyond our expectations, here the results:
> - using 64Gb the "Connection refused" error occured
> - with 96Gb the load has ended successfully
>
> See attached the memory performance graphs during the tests. We suspect
> a *memory leak *issue here... Is there any memory tuning or
> increase/decrease the entity index size? Also we have to know if
> lucenesail is still mantained and further developed, please clarify.
I am not personally involved in the LuceneSail development (it is a
project separate from Sesame, maintained by DFKI), but as far as I know
it is not actively maintained at the moment.
Regards,
Jeen
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Sesame-general mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/sesame-general
_______________________________________________
Nepomuk mailing list
[email protected] <mailto:[email protected]>
https://mail.kde.org/mailman/listinfo/nepomuk
--
Vishesh Handa
--
Sorin Gheorghiu Tel: +49 7531 88-3198
Universität Konstanz Raum: B703
78464 Konstanz [email protected]
- Bibliothek: IT-Abteilung -
_______________________________________________
Nepomuk mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/nepomuk
