yugabyte-db
HikariCP
yugabyte-db | HikariCP | |
---|---|---|
91 | 33 | |
8,580 | 19,564 | |
1.1% | - | |
10.0 | 5.8 | |
5 days ago | about 1 month ago | |
C | Java | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
yugabyte-db
-
Crash on clock skew: performance vs availability
In a distributed database, NTP synchronization is essential and should be carefully monitored and fixed in case of any failures. To allow some time drift, a maximum clock skew is set. This skew should be kept low enough for performance to avoid too many read retries and high enough for availability to avoid any node evictions caused by network errors. It is a good idea to check the NTP synchronization when starting a YugabyteDB node. This will be implemented by 22255.
-
Advisory/Custom/Application Lock with YugabyteDB
Different ways exist to implement locking mechanisms on arbitrary values. For example, PostgreSQL provides pg_advisory_lock, MySQL has get_lock, Oracle Database offers dbms_lock, and SQL Server use sp_getapplock. For YugabyteDB, the PostgreSQL version is not currently supported (#3642).
-
A lightweight YugabyteDB docker image for CI/CD
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.
-
Multi-region YugabyteDB deployment on AWS EKS with Istio
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.
-
Best Practice: use the same datatypes for comparisons, like joins and foreign keys
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.
-
Jonathan Katz: Thoughts on PostgreSQL in 2024
It can be done like https://github.com/yugabyte/yugabyte-db/ has.
-
Is co-partition or interleave necessary in Distributed SQL?
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.
-
PostGIS on YugabyteDB Alma8 (workarounds)
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
-
Bitmap Scan in YugabyteDB
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.
- Yugabyte – distributed PostgreSQL, 100% open source
HikariCP
-
Java virtual threads caused a deadlock in TPC-C for PostgreSQL
Looks like HikariCP is also awaiting fixes for this https://github.com/brettwooldridge/HikariCP/pull/2055
- About Pool Sizing
- HikariCP maximumPoolSize based on AWS ECS number of tasks
-
Writing to db
I have used hikari and exposed to do this in the past with postgres, although other dialects are supported.
-
A Tale of Two Connection Pools
I found one suggestion from the author of HikariCP on how to address this, which I implemented and it worked. However, there are additional classes involved, and it feels a little clunky and hard to follow.
-
Spring boot change password runtime
Not really, you can change some things in spring boot but doing so will typically trigger a refresh which is less reliable than restarting but still causes a large performance hit. You could probably do it with hikari if you really needed to but it's inadvisable to build your application around this mechanic.
-
Help with bungeecord server
# https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Currently load testing a Django API I don’t get good results, Help me brainstorm this
Not familiar with Python but this thread about a Java connection pool might be interesting: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Should I use diesel ORM if performance is the most important thing?
Whatever you choose, presuming your app is database heavy, I highly recommend spending time on DB schema design to make all queries as short as possible, avoid relying on transactions, and keep your connection pool tiny. For reference: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
-
Art of README
You reminded me of the HikariCP library and it’s documentation: Clear and simple with references to other libraries trying to accomplish the same thing. It is not in the closure space though.
https://github.com/brettwooldridge/HikariCP
What are some alternatives?
citus - Distributed PostgreSQL as an extension
c3p0 - a mature, highly concurrent JDBC Connection pooling library, with support for caching and reuse of PreparedStatements.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
spring-boot-r2dbc - An example implementation of Spring Boot R2DBC REST API with PostgreSQL database.
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
Vibur DBCP - Vibur DBCP - concurrent and dynamic JDBC connection pool
psycopg2 - PostgreSQL database adapter for the Python programming language
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
Flyway - Flyway by Redgate • Database Migrations Made Easy.
Apache AGE - Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL. [Moved to: https://github.com/apache/age]
jOOQ - jOOQ is the best way to write SQL in Java