RediSearch VS yugabyte-db

$ git clone https://github.com/RedisGraph/RedisGraph -b v2.4.11 --recurse-submodules -j8 Cloning into 'RedisGraph'... remote: Enumerating objects: 49063, done. remote: Counting objects: 100% (2906/2906), done. remote: Compressing objects: 100% (1082/1082), done. remote: Total 49063 (delta 1998), reused 2448 (delta 1736), pack-reused 46157 Receiving objects: 100% (49063/49063), 39.33 MiB | 114.00 KiB/s, done. Resolving deltas: 100% (38402/38402), done. Submodule 'deps/RediSearch' (https://github.com/RediSearch/RediSearch.git) registered for path 'deps/RediSearch' Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/googletest' Submodule 'deps/libcypher-parser' (https://github.com/RedisGraph/libcypher-parser.git) registered for path 'deps/libcypher-parser' Submodule 'deps/rax' (https://github.com/antirez/rax.git) registered for path 'deps/rax' Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/readies' Submodule 'deps/xxHash' (https://github.com/Cyan4973/xxHash.git) registered for path 'deps/xxHash' Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch'... remote: Enumerating objects: 34395, done. remote: Counting objects: 100% (1802/1802), done. remote: Compressing objects: 100% (1097/1097), done. remote: Total 34395 (delta 1150), reused 1182 (delta 696), pack-reused 32593 Receiving objects: 100% (34395/34395), 23.62 MiB | 71.00 KiB/s, done. Resolving deltas: 100% (25261/25261), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/rax'... remote: Enumerating objects: 668, done. remote: Counting objects: 100% (25/25), done. remote: Compressing objects: 100% (14/14), done. remote: Total 668 (delta 12), reused 19 (delta 11), pack-reused 643 Receiving objects: 100% (668/668), 236.14 KiB | 1.41 MiB/s, done. Resolving deltas: 100% (414/414), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/readies'... remote: Enumerating objects: 2354, done. remote: Counting objects: 100% (833/833), done. remote: Compressing objects: 100% (329/329), done. remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521 Receiving objects: 100% (2354/2354), 390.69 KiB | 17.00 KiB/s, done. Resolving deltas: 100% (1577/1577), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/libcypher-parser'... remote: Enumerating objects: 3250, done. remote: Counting objects: 100% (68/68), done. remote: Compressing objects: 100% (46/46), done. remote: Total 3250 (delta 42), reused 43 (delta 21), pack-reused 3182 Receiving objects: 100% (3250/3250), 2.10 MiB | 28.00 KiB/s, done. Resolving deltas: 100% (2488/2488), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/xxHash'... remote: Enumerating objects: 4784, done. remote: Counting objects: 100% (345/345), done. remote: Compressing objects: 100% (188/188), done. remote: Total 4784 (delta 189), reused 255 (delta 143), pack-reused 4439 Receiving objects: 100% (4784/4784), 2.54 MiB | 27.00 KiB/s, done. Resolving deltas: 100% (2922/2922), done. Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/googletest'... remote: Enumerating objects: 23334, done. remote: Counting objects: 100% (234/234), done. remote: Compressing objects: 100% (142/142), done. remote: Total 23334 (delta 120), reused 146 (delta 81), pack-reused 23100 Receiving objects: 100% (23334/23334), 9.49 MiB | 44.00 KiB/s, done. Resolving deltas: 100% (17191/17191), done. Submodule path 'deps/RediSearch': checked out '68430b3c838374478dd9ffe4e361534f572b16ff' Submodule 'deps/googletest' (https://github.com/google/googletest.git) registered for path 'deps/RediSearch/deps/googletest' Submodule 'deps/readies' (https://github.com/RedisLabsModules/readies.git) registered for path 'deps/RediSearch/deps/readies' Cloning to '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/googletest'... remote: Enumerating objects: 23334, done. remote: Counting objects: 100% (234/234), done. remote: Compressing objects: 100% (148/148), done. remote: Total 23334 (delta 120), reused 141 (delta 75), pack-reused 23100 Receiving objects: 100% (23334/23334), 9.56 MiB | 1.05 MiB/s, done. Resolving deltas: 100% (17185/17185), done. Kloning ke '/home/bpdp/master/postdoc-ugm/RedisGraph/deps/RediSearch/deps/readies'... remote: Enumerating objects: 2354, done. remote: Counting objects: 100% (833/833), done. remote: Compressing objects: 100% (329/329), done. remote: Total 2354 (delta 608), reused 675 (delta 503), pack-reused 1521 Receiving objects: 100% (2354/2354), 390.69 KiB | 853.00 KiB/s, done. Resolving deltas: 100% (1577/1577), done. Submodule path 'deps/RediSearch/deps/googletest': checked out 'dea0216d0c6bc5e63cf5f6c8651cd268668032ec' Submodule path 'deps/RediSearch/deps/readies': checked out '89be267427c7dfcfaab4064942ef0f595f6b1fa3' Submodule path 'deps/googletest': checked out '565f1b848215b77c3732bca345fe76a0431d8b34' Submodule path 'deps/libcypher-parser': checked out '38cdee1867b18644616292c77fe2ac1f2b179537' Submodule path 'deps/rax': checked out 'ba4529f6c836c9ff1296cde12b8557329f5530b7' Submodule path 'deps/readies': checked out 'd59f3ad4e9b3d763eb41df07567111dc94c6ecac' Submodule path 'deps/xxHash': checked out '726c14000ca73886f6258a6998fb34dd567030e9' $

When it comes to production, it is recommended to use the official docker image for YugabyteDB. You can either obtain it from Docker Hub or build it yourself using the Dockerfile. If you are using CI/CD pipelines, it may be helpful to reduce the size of the image. One way to do this is to remove the debug symbols from the compiled binaries. These symbols are useful for troubleshooting but not essential for automated testing. If you encounter any issues, you can easily reproduce them using the regular image.

YugabyteDB is a transactional database that brings together four must-have needs of cloud native apps – namely SQL as a flexible query language, low-latency performance, continuous availability, and globally-distributed scalability. Other databases do not serve all 4 of these needs simultaneously.

It is possible to apply Batched Nested Loop but with additional code that checks the range of the outer bigint and compare it only if it matches the range of integer. This has been added in YugabyteDB 2.21 with #20715 YSQL: Allow BNL on joins over different integer types to help migrations from PostgreSQL with such datatype inconsistencies.

It can be done like https://github.com/yugabyte/yugabyte-db/ has.

Therefore, interleaving or co-partitioning is probably not necessary, and would reduce agility and scalability more than improving the performance. Unless you have a good reason for it that you can share on Issue #79. But, first, test and tune the queries to see if you need something else.

This is a workaround, not supported. I've opened the following issue to get it solve in the YugabyteDB deployment: https://github.com/yugabyte/yugabyte-db/issues/19389

Note that there may still be a need for bitmaps, especially with disjunctions (OR) as the following is about conjunction (AND), and it can still be implemented, differently than PostgreSQL. This is tracked by #4634.

FROM almalinux:8 as build RUN dnf -y update &&\ dnf groupinstall -y 'Development Tools' # get YugabyteDB sources ARG YB_TAG=2.18 RUN git clone --branch ${YB_TAG} https://github.com/yugabyte/yugabyte-db.git WORKDIR yugabyte-db # install dependencies and compilation tools RUN dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm RUN dnf -y install epel-release libatomic rsync python3-devel cmake3 java-1.8.0-openjdk maven npm golang gcc-toolset-12 gcc-toolset-12-libatomic-devel patchelf glibc-langpack-en ccache vim wget python3.11-devel python3.11-pip clang ncurses-devel readline-devel libsqlite3x-devel RUN mkdir /opt/yb-build RUN chown "$USER" /opt/yb-build # Install Python 3 RUN alternatives --remove-all python3 RUN alternatives --remove-all python RUN alternatives --install /usr/bin/python python /usr/bin/python3.11 3 RUN alternatives --install /usr/bin/python3 python3 /usr/bin/python3.11 3 # add #include "pg_yb_utils.h" to src/postgres/src/pl/plpython/plpy_procedure.c RUN sed -e '/#include "postgres.h"/a#include "pg_yb_utils.h"' -i src/postgres/src/pl/plpython/plpy_procedure.c # if using python > 3.9 remove #include and #include from src/postgres/src/pl/plpython/plpython.h RUN sed -e '/#include /d' -e '/#include /d' -i src/postgres/src/pl/plpython/plpython.h # add '--with-python', to python/yugabyte/build_postgres.py under the configure_postgres method RUN sed -e "/'\.\/configure',/a\ '--with-python'," -i python/yugabyte/build_postgres.py # Build and package the release RUN YB_CCACHE_DIR="$HOME/.cache/yb_ccache" ./yb_build.sh -j$(nproc) --clean-all --build-yugabyted-ui --no-linuxbrew --clang15 -f release RUN chmod +x bin/get_clients.sh bin/parse_contention.py bin/yb-check-consistency.py RUN YB_USE_LINUXBREW=0 ./yb_release --force WORKDIR / RUN mv /yugabyte-db/build/yugabyte*.tar.gz /yugabyte.tgz

You have seen me using the official YugabyteDB Docker image extensively. This image is suitable for various purposes, including labs, development, testing, and even production. In the past, we used to create it internally due to its seamless integration with our build process. However, some companies prefer to construct the image on their own, which is indeed a commendable practice. After all, it's not advisable to run random images with root privileges on your servers. As a result, we have made a significant alteration by introducing a refined Dockerfile to our Github repository.