This isn't really a 'load' scenario. I've done more profiling since I started that thread.
A process is creating new RDF on the fly. It just makes 'add' calls to the model obtained from the TDB default graph. There is, sadly, one case which I implemented with reification. When a document wanders by which triggers thousands of these events, the code bogs down. Not so much in adding the reifications, as in checking for existing ones, which is what it has to do. I'm considering a scheme in which I feed the three URI's of the statement into MD5, and 'reifiy' by adding statements like: urn:<md5> HAS_PROVENANCE WHATEVER instead of using the formal reification system. Of course, in an imaginary perfect world, TDB would somehow know about reification.
