• Facets (new session)
• Description
• Metadata
• Settings
  • Rule: ActivityStreamsMapasEquivalentb3sb3sifpfacetshttp://www.w3.org/2002/07/owl#ldpoffers ontologyoplwebrel-me-authschema-oloskos-transurn:det:rdf:labelurn:rdfs:subclass:subproperty:inference:rulesvirtrdf-eturtle-containersvirtrdf-hashtagvirtrdf-ifpvirtrdf-labelvirtrdf-meta-entity-classvirtrdf-urlNone
    
  • Inverse Functional Properties: Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects
  • "Same As": Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects (recommended) Apply to subjects, objects and predicates (not recommended on big datasets) Apply to predicates only (special use cases only)

About: Performance/scalability between these 2 cluster configurations     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:CreativeWork, within Data Space : openlinksw.com associated with source document(s)

Type: CreativeWork New Facet based on Instances of this Class

1st configuration: 4 cluster nodes, 3 instances per cluster node (quorum), 1 instance per cluster host node, 12 cluster host nodes; 2nd configuration: 4 cluster nodes, 3 instances per cluster node (quorum), 4 instances per cluster host node, 12 cluster host nodes: -- This is more to do with how many Virtuoso Server processes are running per cluster node. You will have more OS resources available as the Virtuoso instances are reduced. Ideally, you want to spread the instances over distinct machines so that you have resources pooled across those machines. One instance per cluster node will work better than Four instances per cluster node.