On 27.02.2019 17:27, Jiri Olsa wrote: > On Tue, Feb 26, 2019 at 08:31:38AM +0300, Alexey Budankov wrote: >> >> The patch set implements runtime trace compression (-z option) in >> record mode and trace auto decompression in report and inject modes. >> Streaming Zstandard (Zstd) API (zstd) is used for compression and >> decompression of data that come from kernel mmaped data buffers. >> >> Usage of implemented -z,--compression_level=n option provides ~3-5x >> avg. trace file size reduction on variety of tested workloads what >> saves storage space on larger server systems where trace file size >> can easily reach several tens or even hundreds of GiBs, especially >> when profiling with dwarf-based stacks and tracing of context switches. >> Implemented -f,--mmap-flush option can be used to avoid compressing >> every single byte of data and increase compression ratio at the same >> time lowering tool runtime overhead. Default option value is 1 what >> is equal to the current perf record implementation. The option is >> independent from -z setting and doesn't vary with compression level: >> >> $ tools/perf/perf record -z 1 -e cycles -- matrix.gcc >> $ tools/perf/perf record --aio=1 -z 1 -e cycles -- matrix.gcc >> $ tools/perf/perf record -z 1 -f 1024 -e cycles -- matrix.gcc >> $ tools/perf/perf record --aio=1 -z 1 -f 1024 -e cycles -- matrix.gcc >> >> Runtime compression overhead has been measured for serial and AIO >> trace writing modes when profiling matrix multiplication workload >> with the following results: >> >> ------------------------------------------------------------- >> | SERIAL | AIO-1 | >> ----------------------------------------------------------------- >> |-z | OVH(x) | ratio(x) size(MiB) | OVH(x) | ratio(x) size(MiB) | >> |---------------------------------------------------------------- >> | 0 | 1,00 | 1,000 179,424 | 1,00 | 1,000 187,527 | >> | 1 | 1,04 | 8,427 181,148 | 1,01 | 8,474 188,562 | >> | 2 | 1,07 | 8,055 186,953 | 1,03 | 7,912 191,773 | >> | 3 | 1,04 | 8,283 181,908 | 1,03 | 8,220 191,078 | >> | 5 | 1,09 | 8,101 187,705 | 1,05 | 7,780 190,065 | >> | 8 | 1,05 | 9,217 179,191 | 1,12 | 6,111 193,024 | >> ----------------------------------------------------------------- >> >> OVH = (Execution time with -z N) / (Execution time with -z 0) >> >> ratio - compression ratio >> size - number of bytes that was compressed >> >> size ~= trace file x ratio >> >> See complete description of measurement conditions and details below. >> >> Introduced compression functionality can be disabled or configured from >> the command line using NO_LIBZSTD and LIBZSTD_DIR defines: >> >> $ make -C tools/perf NO_LIBZSTD=1 clean all >> $ make -C tools/perf LIBZSTD_DIR=/path/to/zstd/sources/ clean all >> >> If your system has some version of the zstd package preinstalled then >> the build system finds and uses it during the build. Auto detection >> feature status is reported just before compilation starts, as usual. >> If you still prefer to compile with some version of zstd that is not >> preinstalled you have capability to refer the compilation to that >> version using LIBZSTD_DIR define. >> >> See 'tools/perf/perf test' run results below. >> >> --- >> Alexey Budankov (9): >> feature: implement libzstd check, LIBZSTD_DIR and NO_LIBZSTD defines >> perf record: implement -f,--mmap-flush=<threshold> option >> perf session: define bytes_transferred and bytes_compressed metrics >> perf record: implement COMPRESSED event record and its attributes >> perf mmap: implement dedicated memory buffer for data compression >> perf util: introduce Zstd based streaming compression API >> perf record: implement -z,--compression_level=n option and compression >> perf report: implement record trace decompression >> perf inject: enable COMPRESSED records decompression > > what commit id is this post based on? I can't get it applied:
I think it is that one below: ca9d246ede355946273271c37bf2e9e9fe533212 (HEAD -> zstd.V3) perf inject: enable COMPRESSED records decompression 4a71d4b79f5c1793e4d28851ff0ab11e1b0b2fd9 perf report: implement record trace decompression 5c2ba4e117cfacc415fbeac8e26484cfb80070b7 perf record: implement -z,--compression_level=n option and compression 9634ec18b3090daf5b0137a9aa7dd87552245a83 perf util: introduce Zstd based streaming compression API bc692fb6a1a00e005592233a4ced1198e9d0a78d perf mmap: implement dedicated memory buffer for data compression 9ef63f64522f51bdba9e311303dd8bd73ce88f95 perf record: implement COMPRESSED event record and its attributes 8b470b5b6668532a679cecceeca2e56c1c71b8e2 perf session: define bytes_transferred and bytes_compressed metrics 1666675103895646f78b5f30c9bab77dfbfb91a1 perf record: implement -f,--mmap-flush=<threshold> option 3347a6774f85bcb06a04c95c188eb7f8e99811e1 feature: implement libzstd check, LIBZSTD_DIR and NO_LIBZSTD defines 306b805b097d42e66b0cdae19f97e1d1fa60909e (perf/core) Merge branch 'perf/core' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core => c25b9ecf016e7824096611d4b8b0c6c271205316 (origin/perf/core) perf script python: add Python3 support to syscall-counts-by-pid.py c6e562de9f34fd4df2833a5ef4cf59948385e816 perf script python: add Python3 support to syscall-counts.py b3b4ccaa756984bc81ed7436e55c6fca5d02f00d perf script python: add Python3 support to stat-cpi.py Thanks, Alexey > > Applying: feature: implement libzstd check, LIBZSTD_DIR and NO_LIBZSTD defines > Applying: perf record: implement -f,--mmap-flush=<threshold> option > error: corrupt patch at line 276 > Patch failed at 0002 perf record: implement -f,--mmap-flush=<threshold> option > Use 'git am --show-current-patch' to see the failed patch > When you have resolved this problem, run "git am --continue". > If you prefer to skip this patch, run "git am --skip" instead. > To restore the original branch and stop patching, run "git am --abort". > > > jirka >