[Virtuoso-users] N3 import limit?

[Daniel Alexander Smith]

Hi,

I've been experimenting with virtuoso (open source), and I seem to hit  
a limit of about 200K triples per individually imported N3 file.

When I split up the file, it works fine, so I was just wondering if  
there's something i'm doing wrong, or if I can get around this limit  
somehow.


(Note that i've removed the file in the example below, as it contains  
some non-public data.)


I'm using an N3 file with about 3M triples in it, and the import seems  
fine:

SQL> sparql load "http://helix.ecs.soton.ac.uk/musicspacedata/musicspace-large.n3 
" into graph <musicspace>;
callret-0
VARCHAR
_______________________________________________________________________________

Load <http://helix.ecs.soton.ac.uk/musicspacedata/musicspace- 
large.n3> into graph <musicspace> -- done

1 Rows. -- 5901 msec.


Results are missing, and the number of statements is too low:

SQL> sparql select count(*) where { graph <musicspace> {?d ?f ?g}};
callret-0
INTEGER
_______________________________________________________________________________

222893

1 Rows. -- 20 msec.


The file is ~ 139M, and has 3M+ triples in it (one per line):


helix:musicspacedata das05r$ ls -l
total 135932
-rw-r--r-- 1 root root 139049340 Apr 26 21:33 musicspace-large.n3
helix:musicspacedata das05r$ wc -l musicspace-large.n3
3092038 musicspace-large.n3


I'm using the following version of Virtuoso:

Virtuoso Open Source Edition (multi threaded)
Version 5.0.11.3039-pthreads as of Apr 25 2009
Compiled for Linux (x86_64-unknown-linux-gnu)



Any ideas?


Thanks,

Dan


--
Daniel Alexander Smith

IAM Group
School of Electronics and Computer Science
University of Southampton
das...@ecs.soton.ac.uk