@Andy > Which tdb loader?
I'd guess tdb2.tdbloader since he was replying to my previous email > I loaded truthy, 2.199 billion triples, on a 16G Dell XPS with SSD in 8 hours (76K triples/s) using TDB1 tdbloader2. > > I'll write it up soon. Could you please also share the model names of the hardware components? So we can check the various frequencies, bandwidths, latencies? > The limit at scale is the I/O handling and disk cache. 128G RAM gives a > better disk cache and that server machine probably has better I/O. It's > big enough to fit one whole index (if all RAM is available - and that > depends on the swappiness setting which should be set to zero ideally). Do you have any idea then why executing everything from ramdisk doesn't seem to bring any significant improvements over reading/writing from a SATA3 disk (at least in my tests)?
