This HTML5 document contains 30 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n11:this

foaf:made

n2:VirtMonitorMemoryConsumption

Subject Item

n10:this

sioc:creator_of

n2:VirtMonitorMemoryConsumption

Subject Item

n7:item

n6:services_of

n2:VirtMonitorMemoryConsumption

Subject Item

n14:this

sioc:creator_of

n2:VirtMonitorMemoryConsumption

Subject Item

n5:VOS

sioc:container_of

n2:VirtMonitorMemoryConsumption

atom:entry

n2:VirtMonitorMemoryConsumption

atom:contains

n2:VirtMonitorMemoryConsumption

Subject Item

n2:VirtMonitorMemoryConsumption

rdf:type

sioct:Comment atom:Entry

dcterms:created

2017-06-13T05:41:22.220964

dcterms:modified

2017-06-13T05:41:22.220964

rdfs:label

VirtMonitorMemoryConsumption

foaf:maker

n9:this n11:this

dc:title

VirtMonitorMemoryConsumption

opl:isDescribedUsing

n13:rdf

sioc:has_creator

n14:this n10:this

sioc:content

%META:TOPICPARENT{name="VirtTipsAndTricksGuide"}% ---+ Monitoring Virtuoso Memory Consumption %TOC% ---++ What Like any other process, Virtuoso consumes system resources, including memory. Here we describe one way to monitor the memory consumption of a Virtuoso server instance. ---++ Why monitor memory consumption? In a mission critical application, running 24/7, memory consumption should be fairly consistent when the server is in use. A server should not consume all system memory, which may result in it hanging or being terminated by the operating system. ---++ How to monitor Virtuoso's memory consumption On a Linux or other Unix-like system, you can use a script like this, which we've called <code>memcheck-virtuoso.sh</code>, which checks the memory consumption directly at the process level: <verbatim> #!/bin/bash # saved to /tmp/memcheck-virtuoso.sh pid=$(pidof virtuoso-t); log=/tmp/mem-trace-virtuoso.txt; echo $(printf "%s %s %s" $(date +%FT%R) $(cat /proc/${pid}/status |grep VmSize) ${pid}) | tee -a ${log} </verbatim> This script outputs 3 columns: 1 <code>date-timestamp</code> 2 <code><nowiki>VmSize</nowiki></code>: the actual memsize of the Virtuoso instance (from the <code>cat -> grep</code> for that process id) 3 the process id (or <code>PID</code>) of the Virtuoso instance Here is a sample: <verbatim> $ cat /tmp/memcheck-virtuoso.txt 2014-11-14T17:22 VmSize: 15724332kB 3974 2014-11-14T17:46 VmSize: 15874064kB 3974 2014-11-14T17:55 VmSize: 15874064kB 3974 2014-11-14T18:52 VmSize: 15878076kB 3974 2014-11-14T18:52 VmSize: 15878076kB 3974 2014-11-14T22:29 VmSize: 15878076kB 3974 2014-11-14T22:30 VmSize: 15878076kB 3974 2014-11-14T22:56 VmSize: 15878076kB 3974 2014-11-14T22:56 VmSize: 15878076kB 3974 2014-11-14T23:33 VmSize: 15878076kB 3974 2014-11-14T23:33 VmSize: 15878076kB 3974 2014-11-14T23:52 VmSize: 15878076kB 3974 2014-11-14T23:53 VmSize: 15878076kB 3974 $ </verbatim> The script can be run manually as required. It can also be set up as a cron job to run at a specified internal, e.g., 4 hours in the sample below: <verbatim> $ crontab -l |grep mem 0 */4 * * * /tmp/memcheck-virtuoso.sh </verbatim> ---++ Also See * Technical discussion about [[http://locklessinc.com/articles/memory_usage/][Measuring Memory Usage]]

sioc:id

8055f31ab506004c06a0701456c124c0

sioc:link

n2:VirtMonitorMemoryConsumption

sioc:has_container

n5:VOS

n6:has_services

n7:item

atom:title

VirtMonitorMemoryConsumption

sioc:links_to

n19:

atom:source

n5:VOS

atom:author

n11:this

atom:published

2017-06-13T05:41:22Z

atom:updated

2017-06-13T05:41:22Z

sioc:topic

n5:VOS