Does the number of properties affect performance ? #5342
-
|
Hello, For example, if I have a PRODUCT vertex that has 80 properties, should I separate some properties of that PRODUCT vertex and save it in DETAILS vertex to reduce the number of properties in PRODUCT vertex? Thanks :)) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Dear @PhungQuocLuong-git , Generally, we should be careful when deciding to put info as properties, and yes more properties will require more resources. That is to fetch more data when returning properties/to cache less vertices/edges in same size of block caches of the rocksdb. When properties are needed, don't worry, just put them there, it should work but just be more costly(spawning the cluster with more ram will help). One thing to be highlighted is we should always precisely express your query to only needed properties(when none of the prop is needed, don't return). Regarding whether to put certain things as property or a vertex/edge, it depends on the visit pattern of the system. You could try both and profile their cost with BR//Wey |
Beta Was this translation helpful? Give feedback.
Dear @PhungQuocLuong-git ,
Generally, we should be careful when deciding to put info as properties, and yes more properties will require more resources. That is to fetch more data when returning properties/to cache less vertices/edges in same size of block caches of the rocksdb.
When properties are needed, don't worry, just put them there, it should work but just be more costly(spawning the cluster with more ram will help). One thing to be highlighted is we should always precisely express your query to only needed properties(when none of the prop is needed, don't return).
Regarding whether to put certain things as property or a vertex/edge, it depends on the visit pattern of the system. Y…