Article DetailsDetailsHelp DetailsIssue: During testing, we observed that in Neo4j 5.x, the query planning time is significantly higher compared to previous versions, accounting for nearly 90% of the total query execution time. This extended planning time is affecting all queries. Changes: Migration from Neo4j 4.x to 5.x. Solution: Please increase the server.memory.query_cache.per_db.cache_num_entries setting from the default value of 1000 to 5000. This adjustment expands the query cache capacity, allowing more queries to be reused from cache and reducing the need for repeated query replanning, which can help improve overall performance.InformationTitleIn Neo4j 5.x planning time is significantly higher, when server under loadArticle Created Date8/20/2025, 5:51 AMURL NameIn-Neo4j-5-x-planning-time-is-significantly-higher-when-server-under-loadLast Modified Date11/3/2026, 5:33 AM