Agree w/ Alexis... Tina/Jin Liang, can you please follow-up and make it part of regular check, if this is not done yet?
Thanks, Zhiqiang " Simplicity is Beauty..." -----Original Message----- From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf Of Menard, Alexis Sent: Saturday, August 02, 2014 1:54 AM To: <crosswalk-dev@lists.crosswalk-project.org> Subject: [Crosswalk-dev] Measuring xwalk_core_library size and APKs size produced by make_apk Hi, While working on XWALK-2184, I discovered that make_apk was packing within the final user APK stuff he shouldn't pack in the first place, it was increasing the overall size of the final APK about ~2mb. A PR is on its way to fix and due to this erroneous packing it was triggering the bug on XWALK-2184. Later today some brave user running the canary also told me he saw the size increase. One drawback of Crosswalk is its payload of ~17mb to publish to the store. It's part of our objective to make sure that it doesn't get too bad with the time, that's why I think it's important to make sure it's tracked in our performance or QA reports. Obviously the final APK size will increase/decrease slightly with the time (due to changes in the code) but we shouldn't get big bumps. Something bigger than 1mb is already a problem and probably needs investigation. As we're at it, we should also make sure to track xwalk_core_library which is our other released binary. Again this is important for our users. What you guys think? _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
