Hugh,
On Fri, Oct 4, 2013 at 2:38 PM, Hugh Williams <hwilli...@openlinksw.com> wrote:
> 1. The output of running the "status();" run from command from the Virtuoso
> "isql" commandline tool
====================================
REPORT
VARCHAR
_______________________________________________________________________________
OpenLink Virtuoso Server
Version 07.00.3203-pthreads for Linux as of Aug 12 2013
Started on: 2013-09-24 20:45 GMT+2
Database Status:
File size 6121586688, 747264 pages, 284852 free.
680000 buffers, 95501 used, 1 dirty 0 wired down, repl age 6657939 0
w. io 0 w/crsr.
Disk Usage: 101560 reads avg 0 msec, 0% r 0% w last 0 s, 18062 writes,
450 read ahead, batch = 214. Autocompact 0 in 0 out, 0% saved.
Gate: 624 2nd in reads, 0 gate write waits, 0 in while read 0 busy scrap.
Log = virtuoso.trx, 1595 bytes
462359 pages have been changed since last backup (in checkpoint state)
Current backup timestamp: 0x0000-0x00-0x00
Last backup date: unknown
Clients: 1 connects, max 1 concurrent
RPC: 4 calls, 1 pending, 1 max until now, 0 queued, 0 burst reads
(0%), 0 second 0M large, 1130M max
Checkpoint Remap 0 pages, 0 mapped back. 48 s atomic time.
DB master 747264 total 284852 free 0 remap 0 mapped back
temp 83456 total 83451 free
Lock Status: 0 deadlocks of which 0 2r1w, 0 waits,
Currently 1 threads running 0 threads waiting 0 threads in vdb.
Pending:
Client 1113:1: Account: dba, 224 bytes in, 256 bytes out, 1 stmts.
PID: 3527, OS: unix, Application: unknown, IP#: 127.0.0.1
Transaction status: PENDING, 1 threads.
Locks:
Running Statements:
Time (msec) Text
103 #line 1 "(console)"
status()
Hash indexes
39 Rows. -- 104 msec.
====================================
> 2. The triple count of the database with "select count(*) where {?s ?p ?o};"
130093923
> If you load the data in the Quad Store from an empty database then it will
> be running in column store mode by default.
Yeah, that's what I understood earlier.
> Looking at your INI file I see you have the "NumberOfBuffers" param, which
> is the key to performance in terms of being able to load the database
> working set into memory, set twice:
Ugh... I should have seen that.
> The latter should be commented out or removed and the server restarted, the
> "status()" command will show the buffers allocated and used , which is
> useful to see ...
This is after I shutdown the server, fixed the .ini and started the
server again:
=============================================
REPORT
VARCHAR
_______________________________________________________________________________
OpenLink Virtuoso Server
Version 07.00.3203-pthreads for Linux as of Aug 12 2013
Started on: 2013-10-04 17:39 GMT+2
Database Status:
File size 6121586688, 747264 pages, 284815 free.
680000 buffers, 65559 used, 0 dirty 0 wired down, repl age 0 0 w. io 0 w/crsr.
Disk Usage: 65639 reads avg 0 msec, 0% r 0% w last 0 s, 117 writes,
306 read ahead, batch = 210. Autocompact 0 in 0 out, 0% saved.
Gate: 84 2nd in reads, 0 gate write waits, 0 in while read 0 busy scrap.
Log = virtuoso.trx, 185 bytes
462359 pages have been changed since last backup (in checkpoint state)
Current backup timestamp: 0x0000-0x00-0x00
Last backup date: unknown
Clients: 1 connects, max 1 concurrent
RPC: 4 calls, 1 pending, 1 max until now, 0 queued, 0 burst reads
(0%), 0 second 0M large, 31M max
Checkpoint Remap 38 pages, 0 mapped back. 0 s atomic time.
DB master 747264 total 284815 free 38 remap 0 mapped back
temp 256 total 251 free
Lock Status: 0 deadlocks of which 0 2r1w, 0 waits,
Currently 1 threads running 0 threads waiting 0 threads in vdb.
Pending:
Client 1113:1: Account: dba, 203 bytes in, 256 bytes out, 1 stmts.
PID: 3614, OS: unix, Application: unknown, IP#: 127.0.0.1
Transaction status: PENDING, 1 threads.
Locks:
Running Statements:
Time (msec) Text
70 status()
Hash indexes
37 Rows. -- 71 msec.
=============================================
I am not sure what I should be looking for... it looks like that in
both cases there are many more buffers than those used...
But a query like this doesn't complete before the time out:
SELECT DISTINCT ?property
WHERE { [] ?property [] }
ORDER BY ?property
Let me make clear that I have been really happy with Virtuoso, and
VOS6 has run for a really long time, and I only had to reboot it a few
times in 1-2 years...
Egon
--
Dr E.L. Willighagen
Postdoctoral Researcher
Department of Bioinformatics - BiGCaT
Maastricht University (http://www.bigcat.unimaas.nl/)
Homepage: http://egonw.github.com/
LinkedIn: http://se.linkedin.com/in/egonw
Blog: http://chem-bla-ics.blogspot.com/
PubList: http://www.citeulike.org/user/egonw/tag/papers
ORCID: 0000-0001-7542-0286
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
