arne-bdt commented on issue #3643: URL: https://github.com/apache/jena/issues/3643#issuecomment-3659598225
On the dataset: `bsbm-1m.nt.gz` is not essential for this task from my perspective, and I’d be fine with removing it to keep the repo lean. On the baseline artifacts: my assumption is that `jena-benchmarks-shadedJena560` would be created as part of this task, while the older ones would be dropped. I’m also open to the idea of not having jena-benchmarks built as part of the main reactor (same top-level POM), but I’m not fully sure what the preferred Jena approach would be. But how exactly would that look like? My perspective on keeping `jena-benchmarks` as an asset in the Jena repository: - It took me quite a while to set up initially (I was new to shading and had limited JMH experience). - It was crucial for enabling me to develop and validate `GraphMem2*`. - I used it to develop the COALESCE performance fix and to measure and prove the performance gains. - It helped @Aklakan improve the spatial query index. Overall, I see `jena-benchmarks` as a “red carpet” for Jena developers: a practical place for benchmarks and performance regression checks, with lower setup friction for contributors. -- 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]
