You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,can you please give us some advice on how to use marathon more effectively?
Our setup:
dedicated server with 72 cpu cores + 256Gb RAM, holds up to 72 emulators in docker containers(2 cpu core, 2048ram, 512 vm.heap)
teamcity runs a task:
command line step runs within a docker container which has marathon v8 and open-stf client built-in
we make open-stf connect and work with adb to remove and install our app on every emulator
In total, we have ~300 ui tests running within 11.5minutes
We tried 45 emulators with 4 cpu.cores and 4096ram - but the result is the same = 11minutes
We think it's because of context switching operations at the server CPU.
Maybe we can somehow improve our scheme/configs?Any help highly appreciated, thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,can you please give us some advice on how to use marathon more effectively?
Our setup:
In total, we have ~300 ui tests running within 11.5minutes
We tried 45 emulators with 4 cpu.cores and 4096ram - but the result is the same = 11minutes
We think it's because of context switching operations at the server CPU.
Maybe we can somehow improve our scheme/configs?Any help highly appreciated, thank you!
Beta Was this translation helpful? Give feedback.
All reactions