Runtimes in neo4j community

Hi, I’ve been exploring Neo4j’s runtimes (slotted, pipelined, and parallel) as outlined in these resources:

I believe these runtimes could benefit my use case. However, I’m currently using an 8vCore instance with the Community Edition, and I noticed that the configuration for parallel runtime (internal.cypher.parallel_runtime_support) is disabled by default. After enabling it and trying both pipelined and parallel runtimes, the query profile still shows "interpreted" in both cases. While performance seems improved, I'm unsure if parallel processing is actually being used. Also, is parallel runtime supported in the Community Edition, or could there be issues using it?

Thanks for your insights!

@harshrahamatkar

Although you provide no detail relative to what Neo4j version of software is in use,

and

to which both would suggest Parallel is only available in Enterprise

Thanks, for your response. I'm using Neo4j version 5.9.0.

I’m curious how the internal.cypher.parallel_runtime_support configuration is available to me. Additionally, while using cypher runtime=parallel does seem to improve performance, the profile still shows the runtime as "interpreted." Could you clarify what happens in this interpreted runtime, is it parallel or pipelined?

@harshrahamatkar

internal.**** parameters should generally not be used.
Also as Paralllel runtime was officially GA/introduced in 5.13 and as you are on 5.9 it is unclear what if anything this parameter is doing