Feature request: Add parallel worker support for large APK processing

未关闭
#230 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
android, java
领域
cli, performance

调研方向

Start by reading the CLI argument handling for the decompile and build commands, then trace how the listed resource, DEX/smali, and archive operations are dispatched. The issue does not name specific files or tests, so locate relevant entry points and existing tests before scoping the work. Done means independent tasks can use a configurable worker count, -jobs 1 preserves single-threaded behavior, and output correctness and ordering remain intact.

由索引模型根据 Issue 内容生成。

描述

enhancement

Problem

APKEditor/ARSCLib appears to process many large APK workloads mostly sequentially.

On modern multi-core systems, heavy operations such as resource decoding/encoding, DEX handling, smali disassembly/assembly, and large file scanning/writing do not seem to utilize available CPU cores effectively. This can make processing large applications significantly slower than necessary.

Affected operations

This is noticeable during operations such as:

  • merge
  • decompile
  • compile / rebuild
  • resource decode / encode
  • DEX and smali processing
  • large directory scans
  • archive entry extraction / writing

Example workload

Environment:

  • APKEditor: 1.4.9
  • Input: large APKM with many split APKs, resources, and classes*.dex files
  • JVM example:
java -Xmx8g -jar APKEditor.jar d -i app.apk -o out
java -Xmx8g -jar APKEditor.jar b -i out -o rebuilt.apk

During these operations, CPU usage remains mostly limited instead of scaling across available CPU cores.

Expected behavior

Independent workloads should be processed in parallel where possible, for example:

  • multiple resource files
  • multiple DEX files
  • multiple smali directories or files
  • independent archive entries
  • independent filesystem scan/write tasks

A CLI option to control the worker count would be useful, for example:

-jobs <count>

Example usage:

java -Xmx8g -jar APKEditor.jar d -i app.apk -o out -jobs 8
java -Xmx8g -jar APKEditor.jar b -i out -o rebuilt.apk -jobs 8

Using -jobs 1 could preserve the current single-threaded behavior for compatibility, debugging, or deterministic testing.

Suggested behavior

  • Default behavior could remain unchanged, or use a conservative default such as available processors.
  • -jobs 1 should force single-threaded processing.
  • Parallelization should be applied only to independent tasks where output order and correctness are not affected.
  • Archive output ordering could remain deterministic even if processing is done in parallel.

Impact

Large APK processing is much slower than it could be on multi-core systems. This is especially noticeable for apps with many resource files, split APKs, and multiple DEX files.

Adding controlled parallel processing would improve performance for large workloads while still allowing users to preserve single-threaded behavior when needed.

主要语言
Java
星标
2.3k
派生
417
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

REAndroid/APKEditor 的其他 Issue

查看 REAndroid/APKEditor 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。