The default schema as per the below URL is:
CREATE DISTINCT NO PRIMARY KEY REF BITMAP INDEX RDF_QUAD_SP
ON RDF_QUAD (S, P)
PARTITION (S INT (0hexffff00));
CREATE BITMAP INDEX RDF_QUAD_POGS
ON RDF_QUAD (P, O, G, S)
PARTITION (O VARCHAR (-1, 0hexffff));
CREATE DISTINCT NO PRIMARY KEY REF BITMAP INDEX RDF_QUAD_GS
ON RDF_QUAD (G, S)
PARTITION (S INT (0hexffff00));
CREATE DISTINCT NO PRIMARY KEY REF INDEX RDF_QUAD_OP
ON RDF_QUAD (O, P)
PARTITION (O VARCHAR (-1, 0hexffff));
Given this, I noticed that the below index PGOS uses DB.DBA.RDF_QUAD (G,
P, O, S), shouldn't that be DB.DBA.RDF_QUAD (P, G, O, S)?
- Erich
Hi,
I tried creating the index as per the page:
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFPerformanceTuning
CREATE BITMAP INDEX RDF_QUAD_PGOS ON DB.DBA.RDF_QUAD (G, P, O, S)
PARTITION (O VARCHAR (-1, 0hexffff));
which successfully creates via ISQL (seemingly), but when I go to
execute a bulk load across 8 cores, Virtuoso
dies with a segmentation core dump. The same bulk load works fine
without creating the above index.
Did I miss something in the creation of the index? - Erich
Erich Bremer
http://www.ebremer.com
------------------------------------------------------------------------------
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=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Virtuoso-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
