feat: use rust allocated tuples for binary data

Summarize the changes

• feat: use rust allocated tuples for binary data

Co-authored-by: Georgy Moshkin gmoshkin@picodata.io

Ensure that

• New code is covered by unit and integration tests.
• Related issues would be automatically closed with gitlab's closing pattern (Closes #1, #2).
• Public modules are documented (check the rendered version with cargo doc --open).
• (if PEST grammar is changed) EBNF grammar reflects these changes (check the result with railroad diagram generator.

Next steps

• Cherry-pick to: none / 24.2 / 24.3
• Update sbroad submodule in picodata/picodata.
• (if EBNF grammar is changed) create a follow-up issue in picodata/docs.

Closes #815 (closed)

changed milestone to %24.6 - Plugins and Tiers

added Performance label

assigned to @darthunix

requested review from @senya_volynets

added 1 commit

• 749e25fc - feat: use rust allocated tuples for binary data

Compare with previous version

mentioned in merge request picodata!1271 (closed)

added 8 commits

• 749e25fc...5817d059 - 6 commits from branch main
• b03beb05 - feat: use rust allocated tuples for binary data
• 16ac2578 - fix: migrate to rust-allocated tuples for virtual tables

Compare with previous version

added 1 commit

• 73c29762 - fix: migrate to rust-allocated tuples for virtual tables

Compare with previous version

mentioned in merge request !446 (closed)

added 15 commits

• 73c29762...d766074e - 13 commits from branch main
• 8ad14c9f - feat: use rust allocated tuples for binary data
• 92372682 - fix: migrate to rust-allocated tuples for virtual tables

Compare with previous version

why rust-allocated tuple is better than tarantool-allocated one? Are there any benches?

Correct if I am wrong, this mr improves perfomance by:

1. Wrapping optional and required data in Tuple. This way we reduce overhead when passing data between rust and lua. Earlier we would convert rust object (required/optional) to lua object, now when we pass tuple it is passed as cdata.
2. Serializing bincode directly into tuple data memory. Instead of creating Vec<u8> and then copying it to tuple, we write bincode directly into tuple data memory.

added 3 commits

• 2859cbdb - 1 commit from branch main
• d391da24 - feat: use rust allocated tuples for binary data
• 90c59e4e - fix: migrate to rust-allocated tuples for virtual tables

Compare with previous version

added 3 commits

• 5805162d - feat: use rust allocated tuples for binary data
• b5d250e4 - fix: migrate to rust-allocated tuples for virtual tables
• 2f3dc706 - fix: remove redundant header in encoded vtables

Compare with previous version

approved this merge request

mentioned in issue #825 (moved)