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
According to CPU profiling of a Join test case, a large portion of CPU usage was used to decode/encode datum in the CompactedRow.
As we know, CompactedRow was close to storage formats instead of in-memory format. The idea is, if we can design a new encoding-free in-memory row representation that is close to the StreamChunk or Datum, then we are able to save the cost of decoding & encoding, but rather directly use the reference to do any datum operation.
According to CPU profiling of a Join test case, a large portion of CPU usage was used to decode/encode datum in the
CompactedRow
.As we know,
CompactedRow
was close to storage formats instead of in-memory format. The idea is, if we can design a new encoding-free in-memory row representation that is close to theStreamChunk
orDatum
, then we are able to save the cost of decoding & encoding, but rather directly use the reference to do any datum operation.Context in Slack thread: https://risingwave-labs.slack.com/archives/C034TRPKN1F/p1733731711877629?thread_ts=1733464753.437989&cid=C034TRPKN1F
https://risingwave-labs.slack.com/archives/C034TRPKN1F/p1736135668504179
The text was updated successfully, but these errors were encountered: