> > And I'm not convinced it's a problem of disk cache either, because I tried > > to flush it several times, but the disk was always getting slower and > > slower as more triples were added (1MB/s writes!!!). So, didn't you > > experience the same issue with your 5400rpm disks? > > Your IO is saturated. Not yet but at some point above 200M lines I will > too, so I either reduce the lines or increase the IO (currently on X399 > chipset which supports 8 6G SATA devices). You are looking for the sweet > spot and that's different between hardware. My IO is huge because I'm using > a Ryzen but eventually I'll saturate it.
This is what I don't understand. When I get to 150M/200M loaded triples (1 loader only, single SATA3 disk), CPU load is basically 0%, RAM ~1GB, disk reads around 5-10MB/s, disk writes around 1MB/s, and tdbloader2 performing less than 4K triples per batch. So... what exactly is saturated here? What operation is causing the saturation? And more importantly can I do anything to de-saturate it? Like for instance, I could try to do this every once in a while: 1- send a STOP signal to tdbloader2 to pause the process 2- de-saturate whatever is saturated 3- send a CONTINUE signal to restart tdbloader2 is anything like this remotely possible?
