;http://www.linkedin.com/company/openlink-software/>
> Twitter -- http://twitter.com/OpenLink <http://twitter.com/OpenLink>
> Google+ -- http://plus.google.com/100570109519069333827/
> <http://plus.google.com/100570109519069333827/>
> Facebook -- http://www.facebook.com/OpenLin
Hugh Williams wrote:
> Hi Daniel,
>
> Thanks, I have been able to recreate and reported to development to fix:
>
Thank you very much. I will continue to monitor the mailing list to see if
there is a fix, but it is VOS, so perhaps 7.2.2.
There are still many things that may be done on my end –
.ttl>
>
> I imagine you got the vocabulary file through the site itself, since URLs
> likehttp://id.nlm.nih.gov/mesh/vocab#Descriptor
> <http://id.nlm.nih.gov/mesh/vocab#Descriptor> redirect to it.
>
> From: Hugh Williams [mailto:hwilli...@openlinksw.com]
> Sent: W
.gov/mesh
> <http://id.nlm.nih.gov/mesh> again and again (I used 15 seconds delay) with
> DB.DBA.ttlp().
>
> From: Hugh Williams [mailto:hwilli...@openlinksw.com]
> Sent: Sunday, August 16, 2015 8:52 PM
> To: Davis, Daniel (NIH/NLM) [C]
> Cc: virtuoso-users@lists.sourcef
nih.gov/mesh again and
again (I used 15 seconds delay) with DB.DBA.ttlp().
From: Hugh Williams [mailto:hwilli...@openlinksw.com]
Sent: Sunday, August 16, 2015 8:52 PM
To: Davis, Daniel (NIH/NLM) [C]
Cc: virtuoso-users@lists.sourceforge.net
Subject: Re: [Virtuoso-users] Memory leaks with virtuos
Hi Daniel,
Why were the 7.2.1 & 7.2.0 builds configured with different options, as they
not both being performed on the same OS, in which case I would expect the
configure options to the same ?
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://
Hugh Williams wrote:
> Also, note the following 2 parameters: ThreadCleanupInterval,
> ResourcesCleanupInterval which can both be set to 1 in order to reduce memory
> leaking:
>
>
> http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ex_threadcleanupinterval
>
> although as this wa
On 6 August 2015 at 16:28, Davis, Daniel (NIH/NLM) [C] wrote:
> Hugh Williams wrote:
> > How is this "process to convert MeSH XML to MeSH RDF" which uses lots of
> memory performed, is this done in Virtuoso or by some external process ?
>
> It's really converting to triples - https://github.com/H
Hugh Williams wrote:
> How is this "process to convert MeSH XML to MeSH RDF" which uses lots of
> memory performed, is this done in Virtuoso or by some external process ?
It's really converting to triples - https://github.com/HHS/meshrdf contains the
conversion code, which is basically an XSLT p
Hi Daniel,
Valgrind is probably the most common method of tracking memory problems on
Linux I am aware of.
Please note the following document on monitoring Virtuoso memory consumption:
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtMonitorMemoryConsumption
Also, note
MeSH RDF in production (front-end is http://id.nlm.nih.gov/) is experiencing
Virtuoso memory leaks of virtuoso during our nightly reload of all the MeSH
triples.We noticed these first because virtuoso was being killed by the OOM
killer, either when the process to convert MeSH XML to MeSH RDF
11 matches
Mail list logo
