Re: [lttng-dev] In lttng-live mode, if the printing speed cannot keep up with the generation speed of the parsed ctf data, where will the data be stored?

On Wed, Mar 09, 2022 at 01:26:42AM +0800, 熊毓华 wrote: > If for some reason (for example, here my socket send function in print_message > is blocked and the Babeltrace2 may be suspended), the speed of the reader > (babeltrace2) cannot keep up with the speed of the > producer(lttng/lttng-consumerd),

Re: [lttng-dev] In lttng-live mode, if the printing speed cannot keep up with the generation speed of the parsed ctf data, where will the data be stored?

If for some reason (for example, here my socket send function in print_message is blocked and the Babeltrace2 may be suspended), the speed of the reader (babeltrace2) cannot keep up with the speed of the producer(lttng/lttng-consumerd), can the size of this buffer("lttng-relayd" ) be set? How

Re: [lttng-dev] In lttng-live mode, if the printing speed cannot keep up with the generation speed of the parsed ctf data, where will the data be stored?

Hi > I wonder if my socket recv function is blocked on the other end, causing the > socket send function to block in print_message function in babeltrace2;or when > printing to the console, the printing speed can't keep up with the parsed CTF > data generation speed and the print buffer is also

[lttng-dev] In lttng-live mode, if the printing speed cannot keep up with the generation speed of the parsed ctf data, where will the data be stored?

Hi~ I am getting the trace data using lttng-live mode via babeltrace2. In the final step, I borrowed the code in doc/api/libbabeltrace2/examples/epitome.c. The difference is that in print_message(line 172) in function epitome_out_consume, instead of printing the data directly to the