Feature request: Add parallel worker support for large APK processing

Abierto
#230 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
android, java
Área
cli, performance

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
2.3k
Forks
417
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de REAndroid/APKEditor

Todos los issues de REAndroid/APKEditor

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.