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
- Finshes disk restore feature
- Improved and expanded test suite
- Performance patches
- Improved error handling
- Patches security alerts
- Reduces data need for lazy disk deleter
Copy file name to clipboardExpand all lines: README.md
+8-4
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,12 @@
6
6
GPQ is an extremely fast and flexible priority queue, capable of millions transactions a second. GPQ supports a complex "Double Priority Queue" which allows for priorities to be distributed across N buckets, with each bucket holding a second priority queue which allows for internal escalation and timeouts of items based on parameters the user can specify during submission combined with how frequently you ask GPQ to prioritize the queue.
7
7
</h4>
8
8
9
+
## Notice
10
+
While GPQ is largely stable, bugs are more than likely present at this early stage, and you should carefully consider if your application can tolerate any down time or lost messages that may result from adopting this project into a production workflow. If you run into any bugs please submit an issue or better a PR! Check out the guide to contributing below.
11
+
9
12
10
13
## Table of Contents
14
+
-[Notice](#notice)
11
15
-[Table of Contents](#table-of-contents)
12
16
-[Background](#background)
13
17
- [Should I Use GPQ?](#should-i-use-gpq)
@@ -44,7 +48,7 @@ GPQ is a concurrency safe, embeddable priority queue that can be used in a varie
44
48
45
49
46
50
## Benchmarks
47
-
Due to the fact that most operations are done in constant time `O(1)` or logarithmic time `O(log n)`, with the exception of the prioritize function which happens in linear time `O(n)`, all GPQ operations are extremely fast. A single GPQ can handle a few million transactions a second and can be tuned depending on your work load. I have included some basic benchmarks using C++, Rust, Zig, and Go to measure GPQ's performance against the standard implementations of other languages that can be found here at: [pq-bench](https://github.com/JustinTimperio/pq-bench)
51
+
Due to the fact that most operations are done in constant time `O(1)` or logarithmic time `O(log n)`, with the exception of the prioritize function which happens in linear time `O(n)`, all GPQ operations are extremely fast. A single GPQ can handle a few million transactions a second and can be tuned depending on your work load. I have included some basic benchmarks using C++, Rust, Zig, Python, and Go to measure GPQ's performance against the standard implementations of other languages that can be found here at: [pq-bench](https://github.com/JustinTimperio/pq-bench)
0 commit comments