Jacopo Scazzosi

I'm encountering this in a gRPC client that makes roughly ~1M requests per day, currently using Node.js 10.x. When this happens, all open streams fail and seemingly cannot be recovered....

Hi all. @Limule I did try using Node 14.x and, more recently, 16.x but I'm still getting these errors. However, I should note that moving to newer versions of Node...

Tagging Oxigraph's creator @Tpt just in case he's interested.

@Tpt thank you for that link! I am very curious as to the extent of the performance gap between Oxigraph and Quadstore in the following realms: 1. pure quad ingestion...

Preliminary performance comparison: ```typescript const { strictEqual } = require('assert'); const oxigraph = require('oxigraph'); const { Engine } = require('quadstore-comunica'); const { Quadstore } = require('quadstore'); const { DataFactory }...

Added a couple of tests that should bypass the SPARQL layer in both quadstore and oxigraph (although the latter doesn't seem to support streaming, so we're getting all quads in...

@Tpt interesting! > The results are not surprising to me. JS Oxigraph WASM conversions are very slow so Oxigraph compiled to WASM is only competitive if a lot of computations...

Even more interesting! Oxigraph seems to write roughly 2x faster than quadstore, read 1.5x faster and evaluate SPARQL 5x faster. This is a lot better than I had hoped for...

The comparison I am most interested here, actually, is native Oxigraph on disk (Rust, RocksDB) vs. Quadstore on disk (Node, LevelDB). Quoting from your comments above with slight modifications for...

Closing this as we now have a dedicated test in the [quadstore-perf](https://github.com/belayeng/quadstore-perf) repo and some ideas as to where we stand in comparison to Oxigraph native. Thanks @Tpt !