Variable substitution string in KXmlParser.java file, mobile device handles xml file differences [267108635]

Infeasible

Bug

[AOSP] assigned

NeedsInfo

Status Update

No update yet.

Description

zh...@xiaomi.com

created issue #1

Jan 30, 2023 12:17PM

In the process of Antutu, we found that modifying the KXmlParser.java file on the ssi side (replacing the string<name expected> with variable) can improve Antutu's score of processing xml, so we want to ask whether this is a bug.

Thanks!

Comments

vi...@google.com <vi...@google.com> #2Jan 30, 2023 03:17PM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. OPP1.170223.012)

Which device did you use to reproduce this issue?

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

zh...@xiaomi.com <zh...@xiaomi.com> #3Jan 31, 2023 02:41AM

Android version: T

Problem recurrence: Execute Antutu, and pay attention to the XML processing score

Phenomenon: replace the "name expected" in the KXmlParser.java file on the ssi side with a variable. After modification, the XML processing score of Angora Rabbit improved significantly.

Modify to: static final private String NAME_ EXPECTED = "name expected"; And use NAME_ EXPECTED for subsequent "name expected"

Thanks!

vi...@google.com <vi...@google.com> #4Jan 31, 2023 09:49AM

Thanks for the above information, please share the bug report as requested in comment#2.

zh...@xiaomi.com <zh...@xiaomi.com> #5Feb 2, 2023 11:00AM

bugreport has upload. Thankds!

deleted

Restricted

0 B

deleted

Restricted

0 B

vi...@google.com <vi...@google.com> #6Feb 2, 2023 02:08PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

zh...@xiaomi.com <zh...@xiaomi.com> #7Feb 3, 2023 03:21AM

Okay, thanks!

vi...@google.com <vi...@google.com> #8Feb 14, 2023 01:23PM

Can you tell us if you have the link to the benchmark tests and the scores BEFORE and AFTER applying this change?

zh...@xiaomi.com <zh...@xiaomi.com> #9Feb 15, 2023 03:11AM

The score change is mainly reflected in the data processing in Antutu (including xml and json)

About 45000 before modification

About 49000 after modification

Thanks!

vi...@google.com <vi...@google.com> #10Feb 15, 2023 10:19AM

Thanks for the above information, we have shared this with our product and engineering team and will update this issue with more information as it becomes available.

vi...@google.com <vi...@google.com> #11Feb 16, 2023 10:37AM

Thanks again for the feedback! Our product and engineering teams have evaluated the request and responded:

However, I can't find the source codes of the Antutu benchmarks.

Here are my suggestions, and you can consider one of the following options:

Can you provide the source code of benchmark to reproduce the result? Particularly, why do you mention that it improves the performance of JSON parsing? It would be great that we can reproduce the result and runs the benchmark continuously if the benchmark result is important
If you know how to change the code, you can consider uploading a patch to AOSP directly at http://r.android.com/. We will review it and consider accepting it.

vi...@google.com <vi...@google.com> #12Feb 26, 2023 12:49PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

vi...@google.com <vi...@google.com> #13Mar 6, 2023 12:43PM

Status: Won't Fix (Infeasible)

We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.