cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

v4.4.10 set query is taking more db hits than v4.2.5

hi,

we have a sol. perfectly working on v4.2.5 but due to some reasons we have to upgrade to latest version, but after upgrading we observed that in latest version cypher queries are running slower, when we dig dive into query profiling we found out 2 thing 

  1.  set clause are taking more db hits  in latest db
  2. initial match filtering is also taking extra db hits,
  3. we are not sure about page-caching that is also concern in latest upgrade.

sharing plan for simple query  that we have ran on both versions in 4.2.5 it's taking around 43516 db hits only, but in  v4.4.10 it's around 70561 db hits.

for this simple query we saw profile

profile match(n:commonlabelindex) where n.material_type ='FG' set n.temp =5 
 
 

 

  1. 1. Are there any considerable limitations or considerations while migrating from older neo4j versions to version 4.4.10?
  2.  My graph calculation have gone slower after I started working on 4.4.10 compared to that on 4.2.5? Has anyone else experienced the same?
0 REPLIES 0