On this page
Summary
Together with our global community of contributors, GreptimeDB continues to evolve and flourish as a growing open-source project. We are grateful to each and every one of you.
Below are the highlights among recent commits:
Optimize memory usage during intensive log ingestion
Introducing the new SKIPPING index syntax
Introducing CURSOR statement support for PostgreSQL
Reducing cache size in last-point query scenarios
Reducing IO wait time using prefetching index files from the object store
Introducing the new Log View in the dashboard UI
Contributors
For the past two weeks, our community has been super active with a total of 96 PRs merged. Of these, 4 PRs were contributed by 2 individual contributors, with many more pending to be merged.
A big THANK YOU to all our members and contributors! It is people like you who are making GreptimeDB a great product. Let's build an even greater community together.
Highlights of Recent PRs
db#5135 db#5157 Reduce memory usage under log ingestion
We've conducted a new benchmark under the logging scenario and made major performance improvements upon profiling results. By avoiding holding file caches and memtables during compaction, memory usage is significantly reduced under heavy log ingestion and frequent compaction, from 5.5GB to 500MB at an average level.
db#5095 Reduce cache size in last-point query scenarios
By referencing a new empty batch instead of the old last-row batch, we reduce the cache size in last-point query scenarios from 1GB to 8.3MB under TSBS test cases.
db#5145 db#5146 Reduce IO wait time by prefetching index files
Our index files are stored along with data files in the object store. We've made some improvements using prefetching techniques when queries fall to the object store, reducing wait time from 40ms to 10ms.
db#5155 db#5177 Introducing SKIPPING index syntax
Besides the inverted index and the full-text index, we're developing a new SKIPPING index (implemented using bloom filter) for text searching and matching acceleration. This new type of index will largely reduce the cost of building the full-text index and achieve a similar RT in query scenarios. See the tracking issue here for bloom filter implementation: db#5176.
db#5081 db#5094 Introducing CURSOR statement support for PostgreSQL
Introduce initial support for PostgreSQL's CURSOR statement. We're hoping to be a PostgreSQL foreign data wrapper-compatible server after this series of PRs.
db#5172 Add Log View in GreptimeDB dashboard UI
In the latest release of our integrated dashboard, we introduced the new Log View, which is a new convenient way to observe and search for logs in the database. We're continuously improving the Log View to be a powerful log analysis tool.
More details: Introducing Log View in GreptimeDB Dashboard UI
Good First Issue
db#5120 Implement various vector operation functions
Keywords: Vector
Difficulty: Simple
About Greptime
Greptime offers industry-leading time series database products and solutions to empower IoT and Observability scenarios, enabling enterprises to uncover valuable insights from their data with less time, complexity, and cost.
GreptimeDB is an open-source, high-performance time-series database offering unified storage and analysis for metrics, logs, and events. Try it out instantly with GreptimeCloud, a fully-managed DBaaS solution—no deployment needed!
The Edge-Cloud Integrated Solution combines multimodal edge databases with cloud-based GreptimeDB to optimize IoT edge scenarios, cutting costs while boosting data performance.
Star us on GitHub or join GreptimeDB Community on Slack to get connected.
