[FEATURE] Provide reproducible benchmarks comparing Termux, PRoot and DroidSpaces/chroot

[zFitness]

Is your feature request related to a problem? Please describe.

There is currently little reproducible data comparing the performance of native Termux, PRoot, and DroidSpaces/chroot.

Users often hear that PRoot is slower and chroot is close to native performance, but it is difficult to know the actual difference in CPU, memory, storage, and development workloads.

Describe the solution you'd like

Please provide a reproducible benchmark comparing:

• Native Termux
• proot-distro
• DroidSpaces/chroot

The tests should run on the same device and include:

• CPU and memory performance
• Storage I/O
• Process startup and file operations
• Compression and decompression
• Package installation
• Source code compilation

It would also be helpful to publish the test scripts, device information, environment configuration, and raw results.

Describe alternatives you've considered

Users can run tools such as UnixBench, Sysbench, fio, and hyperfine themselves.

However, results from different users are difficult to compare because devices, storage paths, Linux distributions, and test parameters are different.

Additional context

The goal is not only to prove that DroidSpaces is faster, but to clearly show the advantages and trade-offs of Termux, PRoot, and chroot for real Android Linux workloads.

[ravindu644]

We have no time to do this. There's no war.

Thanks for your understanding.