F2N raven benchmark

[George Lilly]

I copied C0XMAIN.m to C0XF2N.m and ran the qds load on raven (with the
"mm" gtm option). This will give us a benchmark to look at the effect
of various things we try. (F2N stands for Flat file, 2 file, Nodenames
fileman design style - see the abbreviations post)

gpl

GTM>D IMPORT^C0XF2N("qds/qds.rdf")

STARTED: 3111104.152012
READING IN: qds/qds.rdf
73528 LINES READ
ADDED: _:G951670203 _S:805831840 fmts:rdfSource _TXT_INCOMING_RDF_FILE_/home/ge
o
rge/fmts/trunk/samples/qds/qds_rdf_394416761
71530 XML NODES PARSED
PARSE COMPLETE AT 3111104.152023
ELAPSED TIME: 8 SECONDS
APPROXIMATELY 8941 NODES PER SECOND
TRIPLES COMPLETE AT 3111104.153436
ELAPSED TIME: 853 SECONDS
APPROXIMATELY 81 TRIPLES PER SECOND <------ this calculation is
wrong, because "batches" of 10000 nodes at a time were processed mixed
in with the dom node->triple processing
INSERTING 69537 TRIPLES
INSERTION COMPLETE AT 3111104.152023
ELAPSED TIME: 127 SECONDS
APPROXIMATELY 547 NODES PER SECOND <------ I only wish that this were
true, but alas it is based on the time to process the last "batch"
divided by the total number of triples
ENDED AT: 3111104.153643
ELAPSED TIME: 991 SECONDS
APPROXIMATELY 70 TRIPLES PER SECOND <----- this "overall" rate is the
one to watch...

[glilly]

I meant "without the mm gtm option" .. one of the thing I will try
today is the mm option... this is without..

gpl