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 used lots of memory, or when the scripted load of the mesh triples via DB.DBA.ttlp() started.
We are upgrading from Virtuoso 7.2.0 to 7.2.1. Aside from compiling it debug and running this under valgrind, are there any other ways to diagnose memory problems with Virtuoso? Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH
------------------------------------------------------------------------------
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
