Feature #11952
Add "overwrite" parameter to MemoryTracker
Description
Whereas the TimeTracker services has an overwrite parameter that, when set to true, overwrites the contents of the existing database, MemoryTracker does not. The overwrite parameter should be added to the allowed MemoryTracker configuration. In addition, the default for the ntuple::Ntuple::overwrite flag should be reconsidered.
History
#1 Updated by Kyle Knoepfel over 4 years ago
- Status changed from New to Accepted
- Assignee set to Kyle Knoepfel
- Estimated time set to 2.00 h
#2 Updated by Kyle Knoepfel about 4 years ago
- Category set to Infrastructure
- Status changed from Accepted to Resolved
- Target version set to 2.01.00
- % Done changed from 0 to 100
- SSI Package art added
- SSI Package deleted (
)
Implemented with commits art:ccb220b9 and art:6b29a4ab.
There is a change to the MemoryTracker configuration:
MemoryTracker: {
...
- filename: "" # default
+ dbOutput: {
+ filename: "" # default
+ overwrite: false # default
+ }
...
}
The deprecated configuration is still supported, however, the following diagnostic is emitted at the top of the process printout:
The "services.MemoryTracker.filename" parameter is deprecated. It will be replaced
by the following configuration:
services.MemoryTracker.dbOutput: {
filename: "test.db"
overwrite: false
}
MemoryTracker configurations that take the default configuration:
services.MemoryTracker: {}
will not need to be changed.
Also of note, the event-source summary information is no longer reported due to various issues. If reporting the memory usage of creating an event is desired, then another feature request should be made.
#3 Updated by Kyle Knoepfel about 4 years ago
- Status changed from Resolved to Closed