Profiling various
writes dictionary with compression
Activity
- Maintainer
A slight regression in behaviour of the '-profiling' option. Now that memInfo has been made off by default, this command-line option does not enable everything (which would be the expected behaviour).
Edited by Mark OLESEN - Mark OLESEN mentioned in commit d0b84daaf82aa207f8bb780e97fdf153ed1851e1
mentioned in commit d0b84daaf82aa207f8bb780e97fdf153ed1851e1
- Mark OLESEN Status changed to closed
Status changed to closed
- Author Maintainer
Why do we see in above log file
profiling::writeNow() at time = 0 profiling::writeNow() at time = 0
?
- Mattijs Janssens Status changed to reopened
Status changed to reopened
- Author Maintainer
addProfiling macro does not guarantee destruction at end of scope. If it gets early-deleted it might count completely wrong.
- Author Maintainer
Can output written as a dictionary instead of PtrList? Makes it much easier to manipulate (changeDictionaryDict, foamInfoExec)
- Maintainer
Had the idea of writing a dictionary, but there is no natural key other than something like _ID, which seems fairly too arbitrary. As an alternative, could strip out all the non-word chars from the description and try that, but there could be name collisions possible @andy comments?
Edited by Mark OLESEN - Maintainer
profiling::writeNow is explicitly called in snappy since there is no natural time-driven triggering of the writeObject mechanism. time = 0 corresponds to the current time.
- Author Maintainer
Do we want to write to stdout? (I understand we want to write the file) i.e. Info<<"profiling::writeNow() at time = " << pool_->owner().timeName() << endl;
Edited by Mattijs Janssens - Developer
If controlDict has profiling {}
decomposePar throws warning
--> FOAM Warning : From function static void Foam::profiling::initialize(const Foam::dictionary&, const Foam::IOobject&, const Foam::Time&) in file global/profiling/profiling.C at line 126 Already initialized
Also, what about situation when the counters exceed label/scalar threshold ?
- Mark OLESEN mentioned in commit c4c12a0c3559bcb7ae967bb7c5bc7263c0a853ad
mentioned in commit c4c12a0c3559bcb7ae967bb7c5bc7263c0a853ad
- Mark OLESEN mentioned in commit 2dde5ffb41d7ba912562ed238685744fa2b6fee3
mentioned in commit 2dde5ffb41d7ba912562ed238685744fa2b6fee3
- Mark OLESEN mentioned in commit 60d061b93271384b5f4592e89e7e6c685e456476
mentioned in commit 60d061b93271384b5f4592e89e7e6c685e456476
- Admin Status changed to closed by commit d0b84daaf82aa207f8bb780e97fdf153ed1851e1
Status changed to closed by commit d0b84daaf82aa207f8bb780e97fdf153ed1851e1
By Andrew Heather on 2016-06-30T22:09:42 (imported from GitLab project)