On Wed, Jun 13, 2012 at 5:20 AM, Damian Steer <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/06/12 18:47, Benson Margulies wrote: >> I hit the problem I sent mail about most recently whilst trying to >> reproduce the following. Is there any reason to think that this is >> worse than TDB being unlucky enough to be the allocation straw >> that breaks the camel's back? > > What are you running this on? On 64bit machines TDB should be > reasonably light on the heap.
"A whole lot of triples"? It's sitting there stuffing triples into the store, some, as you see, are reifications, which results in some queries, and in other cases we're explicitly querying to decide what to insert. Running the whole business with -Xmx1g succeeds. If there is some more specific characterization of the process that would help, please let me know. I obviously can't deliver the entire circus as a test case. > > Damian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk/YW2IACgkQAyLCB+mTtyn0DgCePSGFRsIMp8PBR9JGzX11nQwM > s+wAn0JSAcF/J+pbXIMRUsinSnDzVPvf > =1C1e > -----END PGP SIGNATURE-----
