> What properties are transitive? Right now, it is just an ontology…so, everything is properties and classes. So, subClassOf and subPropertyOf exist on nearly every subject node.
> Example query? PREFIX : <urn:blah/> PREFIX custom: <http://example.com/> SELECT * WHERE { :42 custom:id ?id } (`:42` has only one `custom:id` triple and has no `owl:sameAs` inference…only “TransitiveReasoner” is being used) On Aug 11, 2021, at 8:29 AM, Andy Seaborne <[email protected]<mailto:[email protected]>> wrote: "EXTERNAL EMAIL" - This email originated from outside of the organization. Do not click or open attachments unless you recognize the sender and know the content is safe. If you are unsure, please contact CTS at [email protected]<mailto:[email protected]>. On 11/08/2021 01:17, Brandon Sara wrote: > Can I get some recommendations on how to best tweak/setup memory for my > fuseki servers? Here is my setup: > > - I’ve got a single TDB with at least several million triples (I don’t know > the exact amount yet, but perhaps around 10s of millions, maybe 100s of > millions…a the very least, I need it to scale to 100s of millions). > - Everything is put in the default graph currently (wanting to change > this…but can’t the this point in time). > - The “TransitiveReasoner” is being used on the dataset. What properties are transitive? (and maybe https://jena.apache.org/documentation/rdfs/?<https://jena.apache.org/documentation/rdfs/?>) > - Full text indexing over two different fields is enabled using Lucene. > - The servers are running embedded Fuseki via rdf-delta and sync via a > central rdf-delta server. > - The simplest of queries won’t finish and runs out of memory with, at the > very least, 6 GB of RAM. Example query? And is the request causing the database to be sync'ed before the request starts? > > Also, should I be tweaking my non-heap memory to be larger for the Fuseki > server? Unlikely. Andy > > Thanks. > > No PHI in Email: PointClickCare and Collective Medical, A PointClickCare > Company, policies prohibit sending protected health information (PHI) by > email, which may violate regulatory requirements. If sending PHI is > necessary, please contact the sender for secure delivery instructions. > > Confidentiality Notice: This email message, including any attachments, is for > the sole use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply email and destroy all copies of the original > message. > No PHI in Email: PointClickCare and Collective Medical, A PointClickCare Company, policies prohibit sending protected health information (PHI) by email, which may violate regulatory requirements. If sending PHI is necessary, please contact the sender for secure delivery instructions. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
