v4.4.10 set queries are taking more db hits than v4.2.5

[shrivastave2000]

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 3 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 

V.4.2.5::

v:4.4.10::

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?

[glilienfield]

are your page cache sizes equivalent between the two environments? 

https://neo4j.com/developer/guide-performance-tuning/#_page_cache_sizing

also, it doesn’t look like you have an index on material_type property for commonlabelindex label. You may reduce the time for the first two boxes in the explain plans, NodeByLabelScan and Filter

[shrivastave2000]

Hi,
yes page cache sizes  are equivalent between the two environments. Also max heap size and initial_heap_size is also same  in both.
I know I can use index on material_type property but I want you show you the db hit diff. when we are searching with some non index based property. you can easily see the db hit diff. there.

[glilienfield]

What lead me to ask the question is the huge difference in the number of page cache hits for the node scan for each environment.  It is a total of 4 pagecache hits for the previous environment, will it is over 70K for the new environment.  Why such a huge difference for the same data? 

[shrivastave2000]

look these are my memory config for both version. I have total 32 gb ram in my system.

db: v4.4.10

dbms.memory.heap.initial_size=20g
dbms.memory.heap.max_size=20g

# The amount of memory to use for mapping the store files.
# The default page cache memory assumes the machine is dedicated to running
# Neo4j, and is heuristically set to 50% of RAM minus the Java heap size.
dbms.memory.pagecache.size=8g
#dbms.query_cache_size=10000

db: v4.2.5

dbms.memory.heap.initial_size=20g
dbms.memory.heap.max_size=20g

# The amount of memory to use for mapping the store files.
# The default page cache memory assumes the machine is dedicated to running
# Neo4j, and is heuristically set to 50% of RAM minus the Java heap size.
dbms.memory.pagecache.size=8g

[shrivastave2000]

I am still waiting for reply from @neo4j  team