platform_system_core/logcat/tests
Mark Salyzyn fbc0fe429b logcat: test: run 256 simultaneous logcats
For logd daemon, heavy reader stress. For system popen fork and
execute of logcat measure baseline against liblogcat. For liblogcat
local concurrent thread, locking, argument parsing and context scaling
for popen-style pair of android_logcat_run_command_thread* functions.

NB: 1000 logcat executables ran, but did not scale well on time
    blocked for more than a minute. With 343 contexts of
    android_logcat_run_command_thread ran out of local resources
    to even return a file descriptor, and the per-context event tag
    mappings coincidentally ran out at 340 when threads ran, although
    that path was consistently 15% faster than the popen test.

Test: gtest logcat-unit-tests --gtest_filter=*.End_to_End_multitude
Bug: 35326290
Change-Id: I0e1a5d4f8ffbd77fa8db13d53f4d328973731895
2017-03-27 11:57:53 -07:00
..
Android.mk liblogcat: measure performance 2017-02-22 16:06:24 -08:00
exec_benchmark.cpp liblogcat: measure performance 2017-02-22 16:06:24 -08:00
liblogcat_test.cpp liblogcat: add android_logcat_popen and android_logcat_system 2017-02-17 14:42:14 -08:00
logcat_benchmark.cpp liblogcat: measure performance 2017-02-22 16:06:24 -08:00
logcat_test.cpp logcat: test: run 256 simultaneous logcats 2017-03-27 11:57:53 -07:00