The numbers below have been derived based on your current data volume in database and index configuration of database 'graph.db'. They can be used as an input into more detailed memory analysis.
Lucene indexes: 47800m
Data volume and native indexes: 129600m
I am not sure I should be more generous with lucene memory or page cache for my scenario.
My application is more write intensive than read. With limited memory what should be recommended memory setting to make it biased towards write.
Thanks Stefen, just one doubt, as far as i know lecune index is not part of memory which we assign for page cache and its the left over memory after page cache and heap which is used by lecune and system os. So is it fair to leave only 8gb for it(for wtite biased scenarios)
I've implicitly assumed you're on 3.4 which offers native indexes for almost every scenario. YMMV when being on previous versions.
You're right Lucene uses off-heap memory as well which is not controlled via pagecache size settings.
I have migrated from 3.2.5 to 3.4.7 along with data. and recreated index. But above memrec output still shows 47g of lucene index. is it normal that i still have 47g of lucene index?