Feature request: Add parallel worker support for large APK processing
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
- Á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
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*.dexfiles - 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 1should 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de REAndroid/APKEditor
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
-
enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Todos los issues de REAndroid/APKEditor
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
jenkins-infra/plugin-modernizer-tool#2070 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Event search answers 500 when calendars, attendees or organizers holds a null elementQuizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertoai-driven-qa bug Minor
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
linagora/twake-calendar-side-service#1615 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
eclipse-tradista/tradista#371 ·
Los mantenedores suelen responder en 1 día
-
Failed to start Rescue missionAbiertocritical
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
mars-sim/mars-sim#2199 · 2 comentarios ·
Los mantenedores suelen responder en 1 día