Status Update
Comments
cc...@google.com <cc...@google.com> #2
Can you attach a sample trace? I want to see what the separate process is called in the trace
an...@google.com <an...@google.com> #3
The name of the process shows up as
an...@google.com <an...@google.com>
cc...@google.com <cc...@google.com> #4
Can you attach a perfetto trace, rather than a systrace, for example from a macrobenchmark run which didn't collect the metrics that you wanted? Perfetto will capture process names in a different way than systrace (by dumping them during the test run).
Will the sdk sandbox process always have the app's package name, plus the suffix _sdk_sandbox
? Are there sample apps or macrobenchmark target apps in the Jetpack repo I can look at?
an...@google.com <an...@google.com> #5
The tests haven't been submitted yet, I am still doing running the tests locally (aosp/3459800), not sure how I can share the perfetto trace. This is the target
Will the sdk sandbox process always have the app's package name, plus the suffix _sdk_sandbox?
I have seen this in all the local testing I have done. But if it is better to wait till we have submitted tests we can do that. Currently no traces are being collected in the app.
an...@google.com <an...@google.com> #6
Will the sdk sandbox process always have the app's package name, plus the suffix _sdk_sandbox?
Yes, this is always true:
Description
For PrivacySandbox enabled apps, Ad SDK code will run in the Runtime process (every app has its own Runtime process). Adding a feature to get memory metrics for a particular process (the Runtime process for our case - this can be found using getAppUidUsingSandboxUid() API) will be useful for us.