Hi Lorenz,
You might specifically be bumping up against the e2e test that had
been commented out but was uncommented in a recent commit. You may be
able to just comment out the specific e2e yarn and still retain the
others. I commented on a github issue relating to this here:
https://github.com/
Ah, that makes sense. The e2e tests are indeed using 3030
https://github.com/apache/jena/blob/748fc2d0c2b3e397bd2571a29c71106f840505ae/jena-fuseki2/jena-fuseki-ui/src/services/mock/json-server.js#L18
If I recall correctly, there is a way to configure it so the port is
dynamic. And I'd be OK with
Hi,
we're trying to load our project internal data set
with currently 959,170,877 quads (still growing)
on a
24-core AMD EPYC 7443P with 2.85-4.00GHz
256GB RAM
and Samsung SSD 870 QVO 8TB SATA SSDs in a RAIDZ1
tdb2.tdbloader --loader=parallel
21,450.519 seconds
especially noticeable toward
How does this compare with your groups previous loader performance
investigations? Did any use PCIe/m2?
On 18/11/2022 19:52, Simon Bin wrote:
Hi,
we're trying to load our project internal data set
with currently 959,170,877 quads (still growing)
on a
24-core AMD EPYC 7443P with 2.85-4.00GH
afs commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1026914338
##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
Review Comment:
Th