HackerTrans
TopNewTrendsCommentsPastAskShowJobs

tingfirst

no profile record

Submissions

Hybrid Hash Join – breaking the memory wall of streams join

timeplus.com
2 points·by tingfirst·il y a 8 mois·1 comments

Any pipeline tool for ClickHouse, similar to Snowflake's Dynamic Tables

snowflake.com
2 points·by tingfirst·il y a 10 mois·6 comments

OCaml for Kafka stream processing, analytics and telemetry data

github.com
4 points·by tingfirst·il y a 10 mois·3 comments

comments

tingfirst
·il y a 4 mois·discuss
Makes sense if you prefer scanning the whole picture first. Whole-to-parts vs. parts-to-whole is a different mindset. I personally like fade-in in some cases—it helps me focus on one layer at a time and build up the full context without getting overwhelmed. That said, efficiency can be an issue, so each viz is situational and easy to overuse :-)
tingfirst
·il y a 5 mois·discuss
Temporal binding is one of the hardest problems in visualization, all about aggregations across different time windows.

And it gets even harder when the clock never stops and live data keeps flowing.

Client visualization layer: Timeplus Vistral (https://github.com/timeplus-io/vistral)

Server data processing layer: Timeplus Proton (https://github.com/timeplus-io/proton)

Streaming-native from processing to insights in motion
tingfirst
·il y a 8 mois·discuss
All streaming processors face the same fundamental problem:

Streaming joins require maintaining state for both sides of the join

High-cardinality data (millions of unique keys) means huge state sizes

Traditional approach: Keep everything in memory will make memory exhausted

The high-cardinality join memory problem isn't unique to Timeplus. Apache Flink also uses hybrid hash joins that spill to disk (RocksDB) when memory fills, Materialize shares indexed state across multiple queries (but still requires keeping full datasets in memory), and RisingWave stores state in cloud object storage (S3/GCS) with LRU caching for hot data. What makes Timeplus different is its purpose-built optimization for the Pareto Principle, where a tiny fraction of data generates the vast majority of activity - keeping hot data in memory and cold data on disk for dramatic memory savings.
tingfirst
·il y a 9 mois·discuss
Redpanda + Timeplus, the perfect pair for data streaming developers. No JVM, ZK ...
tingfirst
·il y a 9 mois·discuss
Probably the smallest yet most powerful binary for real-time, incremental SQL data processing, end to end!
tingfirst
·il y a 10 mois·discuss
Consistently we heard about ClickHouse has very limited materialized views that can't handle real-time pipeline fast efficiently enough. would love to see more comments here.
tingfirst
·il y a 10 mois·discuss
Data sources are usually in Kafka, or other operational databases like Postgres or MySQL

1. Table A : fact events, high-throughput (10k~1M eps), high-cardinality

2. Table B, C, D : couple of dimension tables (fast or slow changing).

The use case is straightforward : join/enrich/lookup everything into one big flattened, analytics-friendly table into ClickHouse.

What’s the best pipeline approach to achieve this in real-time and efficiently?
tingfirst
·il y a 10 mois·discuss
Is there a native SQL pipeline tool for ClickHouse that processes real-time data incrementally, with low latency, large throughput and high efficiency, similar to Snowflake’s Dynamic Tables?

[1] Dynamic Tables: One of Snowflake’s Fastest-Adopted Features: https://www.snowflake.com/en/blog/reimagine-batch-streaming-...
tingfirst
·il y a 10 mois·discuss
For parallel programming, what's OS-level difference compared to languages like Python or modern C++?

Domain.spawn (fun _ -> print_endline "I ran in parallel")

Anyway, love the simplicity of this expression!
tingfirst
·il y a 10 mois·discuss
AI can be hallucination but real-time detection is key
tingfirst
·il y a 10 mois·discuss
re EPS and CPU utilization, WS still performs better than SSE?
tingfirst
·il y a 10 mois·discuss
For OCaml users interested in data streaming processing (similar to Flink or Spark), but looking for a faster and more efficient option, check out this OCaml plugin Timeplus Proton. Concise, safe, highly performant and fun

-> Streaming Queries - Process large datasets with constant memory usage

-> Async Inserts - High-throughput data ingestion with automatic batching

-> Compression - LZ4 and ZSTD support for reduced network overhead

-> TLS Security - Secure connections with certificate validation

-> Connection Pooling - Efficient resource management for high-concurrency applications

-> Rich Data Types - Full support for #ClickHouse types including Arrays, Maps, Enums, DateTime64

-> Idiomatic OCaml - Functional API leveraging OCaml's strengths
tingfirst
·il y a 10 mois·discuss
For OCaml users interested in data streaming processing (similar to Flink or Spark), but looking for a faster and more efficient option, check out this OCaml plugin Timeplus Proton. Concise, safe, highly performant and fun!

[1] https://github.com/mfreeman451/proton-ocaml-driver