This adds support for ASan both in rust code and core tarantool. To build with ASan, simply run

```bash
make build-asan
```

Keep in mind that ASan-enabled executable lives in

```
target/x86_64-unknown-linux-gnu/asan/picodata
```

as opposed to

```
target/debug/picodata
```

This patch boils down to the following improvements:

* Various linkage-related shenanigans have been documented and revamped.
* All logic to build tarantool-sys is now encapsulated in tarantool-build.
* Most of the magic `println!`s are now encapsulated in build-rs-helpers.
* Unsound function `export_symbols` has been dropped in favor of
  explicit linker flags (`--require-defined` for linux & `-u` for mac).
* `TarantoolBuildRoot` is now in charge of building and linking
  tarantool libs. It defines the build tree via path helper functions.
* Picodata's `build.rs` should be a little easier to read.

Maksim Kaitmazian authored 4 months ago and Maksim Kaitmazian committed 4 months ago

As shown in
https://git.picodata.io/picodata/picodata/picodata/-/issues/1026#note_107222,
enabling LTO and using only one codegen unit can accelerate some
scenarios by 16.89%.

This commit adds these options to the "release" profile. However, it makes
the build much slower, so a new profile "fast-release" is added to address
this problem in CI. The "release" profile will only be used when merging
to master.

Maksim Kaitmazian authored 4 months ago and Dmitry Ivanov committed 4 months ago

Disabling the tracing feature has shown a significant performance improvement
of 72.50%, as demonstrated in https://git.picodata.io/picodata/picodata/picodata/-/issues/1026#note_107222.

This commit disables "tracing" feature for sbroad and eliminates
the opentelemetry wrappers and statistics tables.

picoplugin -> picodata-plugin
picoplugin_gen -> picodata-plugin-proc-macro

This commit embeds in plugins a new variable, containing picoplugin
version used to build it. If this version differs from the picodata version
when the plugin gets loaded, the loading fails with an error reporting
the expected and the current versions. This check can be disabled via env
PICODATA_UNSAFE_DISABLE_PLUGIN_COMPATIBILITY_CHECK.

Maksim Kaitmazian authored 5 months ago and Maksim Kaitmazian committed 5 months ago

This commit resolves the performance issues observed in pgbench
benchmark*. Because of the Nagle's algorithm, every message was read with
50ms delay, while the query execution took only 1ms. By disabling the
algorithm via TCP_NODELAY option, we achieve 50 times performance
improvement for a single client in simple query mode.

* https://git.picodata.io/picodata/picodata/picodata/-/issues/1002

Up to this patch `instance_uuid` and `replicaset_uuid` were generated
using name-based UUID v3. So all instances named `i1` in all clusters
had the same UUID.

With this patch UUIDs become random v4. Particular UUID values are
generated in two locations:

1. `start_boot` (src/lib.rs)
2. `handle_join_request_and_wait` -> `build_instance` (src/rpc/join.rs)

Function `Instance::new()` is removed in favor of explicit struct
construction.

godzie44 authored 8 months ago and Maksim Kaitmazian committed 7 months ago

Closes #584

Dmitry Rodionov authored 7 months ago and Dmitry Ivanov committed 7 months ago

> cargo tree -i either
either v1.13.0
├── itertools v0.10.5
│   └── sbroad-core v0.1.0 (picodata/sbroad/sbroad-core)
│       └── picodata v24.5.0 (picodata/picodata)

feature(plugin migration): use md5 from migration files meta for to confirm consistency of migrations between versions

Closes #652

The problem appeared in form of a failed debian package build. aws-lc-rs
build script was failing with:

thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.19.0/builder/cc_builder.rs:244:13:
Your compiler (cc) is not supported due to a memcmp related bug
reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189.We
strongly recommend against using this compiler.

Since we use system openssl we dont need to rely on these backends.

Error message is probably correct, so upgrading the compiler is still a
good idea.

See: https://git.picodata.io/picodata/picodata/picodata/-/issues/630

godzie44 authored 10 months ago and Georgy Moshkin committed 9 months ago

- add description field to `_pico_plugin` and `_pico_service`
- plugin loading: filter files by its extensions
- plugin loading: check possible service collisions
- plugin loading: now plugin searching at {plugin_dir}/{plugin_name} path
- now all errors between plugin and picodata wrapping with `BoxError` (this protects plugin caller from UAF)

We have recently replaced String with SmolStr in sbroad.
As a result, we need to make corresponding changes in
picodata as it uses sbroad-core for cluster SQL.