Feature request: Add parallel worker support for large APK processing

Aperta
#230 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
android, java
Ambito
cli, performance

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Java
Stelle
2.3k
Fork
417
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di REAndroid/APKEditor

Tutte le issue di REAndroid/APKEditor

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.