afs commented on PR #1918:
URL: https://github.com/apache/jena/pull/1918#issuecomment-1604828082

   I tried 50M and 100m BSBM using the async parser to keep the parser work on 
another thread.
   
   The data files wre on an NVMe SSD.
   Heap size: -Xmx40G
   
   <details>
   <summary>Results for BSBM 50m</summary>
   
   ```
   **** GraphMem2Roaring ****
   **** Data: bsbm-50m.nt.gz ****
   Load time  = 116.362 s
   Load rate  = 429,742 TPS
   Load space = 15,970M 
   
   **** GraphMem2Fast ****
   **** Data: bsbm-50m.nt.gz ****
   Load time  = 117.762 s
   Load rate  = 424,633 TPS
   Load space = 16,347M 
   
   **** GraphMem2Legacy ****
   **** Data: bsbm-50m.nt.gz ****
   Load time  = 120.876 s
   Load rate  = 413,694 TPS
   Load space = 18,169M 
   
   **** GraphMem ****
   **** Data: bsbm-50m.nt.gz ****
   Load time  = 121.770 s
   Load rate  = 410,656 TPS
   Load space = 20,081M 
   ```
   
   </details>
   
   and
   
   <details><summary>Results for BSBM 100m</summary>
   
   ```
   **** GraphMem2Roaring ****
   **** Data: bsbm-100m.nt.gz ****
   Load time  = 235.356 s
   Load rate  = 424,891 TPS
   Load space = 31,733M 
   
   **** GraphMem2Fast ****
   **** Data: bsbm-100m.nt.gz ****
   Load time  = 238.313 s
   Load rate  = 419,619 TPS
   Load space = 32,143M 
   
   **** GraphMem2Legacy ****
   **** Data: bsbm-100m.nt.gz ****
   Load time  = 249.471 s
   Load rate  = 400,851 TPS
   Load space = 35,811M 
   
   **** GraphMem ****
   **** Data: bsbm-100m.nt.gz ****
   Load time  = 259.397 s
   Load rate  = 385,512 TPS
   Load space = 39,582M 
   ```
   
   </details>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to