What does your domain look like when it comes to number of edges, edge
types, nodes, etc? Does all edge types have the `weight` property?
Considering all different relationships compared to only one type will make
a huge difference in performance if there are many other types.
I limit the search to a single type of edge then it works but if I
> consider multiple paths, the query times out.
I just want to make sure I understand you correctly.
Does the query times out when asking for multiple paths even when only
considering one type of edge? Or does that happen when considering all
types of edges?
On Friday, June 5, 2015 at 9:45:24 PM UTC+2, sck2015 wrote:
>
> Hi, I am running use the rest api, anything that requires multiple paths
> to be returned is extremely slow, are there configuration properties I can
> update in the conf directory...
> I am running neo4j-community-2.3.0-M01 and have a box with 18G free ram.
>
> If I want to find something that considers all types of edges
> (relationships), I was using the following json, can someone verify that
> this is correct:
> curl -v -X POST -H 'Content-Type: application/json' -H 'Accept:
> application/json; charset=UTF-8' -d '{ "to": "
> http://localhost:7474/db/data/node/79365","cost_property": "weight",
> "algorithm": "dijkstra" }' http://localhost:7474/db/data/node/902/path
>
> I simply omitted the relationships attribute, I limit the search to a
> single type of edge then it works but if I consider multiple paths, the
> query times out. This should be straightforward I would think.
>
> I also updated conf/neo4j.properties with the following values, please
> advise if there is anything else I should do to optimize the search:
> ################################################################
> # Neo4j
> #
> # neo4j.properties - database tuning parameters
> #
> ################################################################
>
> # Enable this to be able to upgrade a store from an older version.
> #allow_store_upgrade=true
>
> # The amount of memory to use for mapping the store files, in bytes (or
> # kilobytes with the 'k' suffix, megabytes with 'm' and gigabytes with
> 'g').
> # If Neo4j is running on a dedicated server, then it is generally
> recommended
> # to leave about 2-4 gigabytes for the operating system, give the JVM
> enough
> # heap to hold all your transaction state and query context, and then
> leave the
> # rest for the page cache.
> # The default page cache memory assumes the machine is dedicated to running
> # Neo4j, and is heuristically set to 75% of RAM minus the max Java heap
> size.
> dbms.pagecache.memory=10g
>
> # Enable this to specify a parser other than the default one.
> #cypher_parser_version=2.0
>
> # Keep logical logs, helps debugging but uses more disk space, enabled for
> # legacy reasons To limit space needed to store historical logs use values
> such
> # as: "7 days" or "100M size" instead of "true".
> #keep_logical_logs=7 days
>
> # Autoindexing
>
> # Enable auto-indexing for nodes, default is false.
> #node_auto_indexing=true
>
> # The node property keys to be auto-indexed, if enabled.
> #node_keys_indexable=name,age
>
> # Enable auto-indexing for relationships, default is false.
> relationship_auto_indexing=true
>
> # The relationship property keys to be auto-indexed, if enabled.
> #relationship_keys_indexable=name,age
> relationship_keys_indexable=weight
>
> # Enable shell server so that remote clients can connect via Neo4j shell.
> #remote_shell_enabled=true
> # The network interface IP the shell will listen on (use 0.0.0 for all
> interfaces).
> #remote_shell_host=127.0.0.1
> # The port the shell will listen on, default is 1337.
> #remote_shell_port=1337
>
> # The type of cache to use for nodes and relationships.
> #cache_type=soft
>
> use_memory_mapped_buffers=true
> neostore.nodestore.db.mapped_memory=5G
> neostore.relationshipstore.db.mapped_memory=5G
> neostore.propertystore.db.mapped_memory=5G
> neostore.propertystore.db.strings.mapped_memory=5G
> neostore.propertystore.db.arrays.mapped_memory=5G
> cache_type=gcr
> node_cache_size=5G
> relationship_cache_size=5G
>
>
On Friday, June 5, 2015 at 9:45:24 PM UTC+2, sck2015 wrote:
>
> Hi, I am running use the rest api, anything that requires multiple paths
> to be returned is extremely slow, are there configuration properties I can
> update in the conf directory...
> I am running neo4j-community-2.3.0-M01 and have a box with 18G free ram.
>
> If I want to find something that considers all types of edges
> (relationships), I was using the following json, can someone verify that
> this is correct:
> curl -v -X POST -H 'Content-Type: application/json' -H 'Accept:
> application/json; charset=UTF-8' -d '{ "to": "
> http://localhost:7474/db/data/node/79365","cost_property": "weight",
> "algorithm": "dijkstra" }' http://localhost:7474/db/data/node/902/path
>
> I simply omitted the relationships attribute, I limit the search to a
> single type of edge then it works but if I consider multiple paths, the
> query times out. This should be straightforward I would think.
>
> I also updated conf/neo4j.properties with the following values, please
> advise if there is anything else I should do to optimize the search:
> ################################################################
> # Neo4j
> #
> # neo4j.properties - database tuning parameters
> #
> ################################################################
>
> # Enable this to be able to upgrade a store from an older version.
> #allow_store_upgrade=true
>
> # The amount of memory to use for mapping the store files, in bytes (or
> # kilobytes with the 'k' suffix, megabytes with 'm' and gigabytes with
> 'g').
> # If Neo4j is running on a dedicated server, then it is generally
> recommended
> # to leave about 2-4 gigabytes for the operating system, give the JVM
> enough
> # heap to hold all your transaction state and query context, and then
> leave the
> # rest for the page cache.
> # The default page cache memory assumes the machine is dedicated to running
> # Neo4j, and is heuristically set to 75% of RAM minus the max Java heap
> size.
> dbms.pagecache.memory=10g
>
> # Enable this to specify a parser other than the default one.
> #cypher_parser_version=2.0
>
> # Keep logical logs, helps debugging but uses more disk space, enabled for
> # legacy reasons To limit space needed to store historical logs use values
> such
> # as: "7 days" or "100M size" instead of "true".
> #keep_logical_logs=7 days
>
> # Autoindexing
>
> # Enable auto-indexing for nodes, default is false.
> #node_auto_indexing=true
>
> # The node property keys to be auto-indexed, if enabled.
> #node_keys_indexable=name,age
>
> # Enable auto-indexing for relationships, default is false.
> relationship_auto_indexing=true
>
> # The relationship property keys to be auto-indexed, if enabled.
> #relationship_keys_indexable=name,age
> relationship_keys_indexable=weight
>
> # Enable shell server so that remote clients can connect via Neo4j shell.
> #remote_shell_enabled=true
> # The network interface IP the shell will listen on (use 0.0.0 for all
> interfaces).
> #remote_shell_host=127.0.0.1
> # The port the shell will listen on, default is 1337.
> #remote_shell_port=1337
>
> # The type of cache to use for nodes and relationships.
> #cache_type=soft
>
> use_memory_mapped_buffers=true
> neostore.nodestore.db.mapped_memory=5G
> neostore.relationshipstore.db.mapped_memory=5G
> neostore.propertystore.db.mapped_memory=5G
> neostore.propertystore.db.strings.mapped_memory=5G
> neostore.propertystore.db.arrays.mapped_memory=5G
> cache_type=gcr
> node_cache_size=5G
> relationship_cache_size=5G
>
>
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
