profiling improvements

• Would be nice for memory profiling to also record the free memory on each node. This determines when swapping is about to start. E.g.

grep 'MemFree' /proc/meminfo

Just added parsing for MemFree into memInfo. As well as normal profiling, I wonder if it'd be useful as a function-object style (emit warning when things are getting tight).

I've been mulling some other ideas about function-objects, but doesn't quite fit here (discuss by telephone).

perhaps some runTimeControl ?

• fv solvers do not grow memory (- lagrangian might)
• mesh generators are generally the problem and these do not use runTime++ (but do use profiling)
• so any trigger should be added to the profiling instead?

changed title from profiling does not show free memory on node to profiling improvements

changed the description

mentioned in commit e6137408103c4b7bf899430c637512e80c30d1de

mentioned in merge request !178 (merged)

works.

closed