Open polina-c opened 1 year ago
@bkonyi
@polina-c would it make sense to implement this functionality in dart:developer similar to how we added reachabilityBarrier
. Also to clarify we can provide this information only per isolate group and not for individual isolates in the isolate group.
dart:developer is a good place
What is relation between isolate group and process? If a process may contain many isolate groups, I want also to be able to get all of them and total. It is because I want to be able to see how dart vm numbers relate to process monitor numbers on the device.
What is relation between isolate group and process? If a process may contain many isolate groups, I want also to be able to get all of them and total. It is because I want to be able to see how dart vm numbers relate to process monitor numbers on the device.
It is possible to have multiple isolate groups in a process and multiple isolates in one isolate group. We could provide information about the group in which the current isolate exists. IsolateGroups is exposed at the Dart level only through vm-service. we would be able to surface the number only for the current isolate in dart:developer.
Is it possible at least to get number of isolate groups in the process? Then, if the number is 1, I know I can compare the memory totals with numbers in activity monitor, that may help to understand how these numbers relate to each other.
Currently only memory numbers that is exposed to dart isolate are rss numbers:
It would be good to get more cheaply accessible numbers, like like currentIsolateHeap, totalHeap and whatever else is easy to expose in ProcessInfo.
It is needed to measure how a change in the code impacts memory consumption, by running the same test on the same machine 1000 times before change and after change, and recording the numbers.
I do not know which numbers will help. To run experiments that will show it, I need access to the numbers in a cheap way.
This is what my prototype outputs based on
currentRss
:See PR: https://github.com/dart-lang/leak_tracker/pull/114