-
We have two general methods for introducing and exfiltrating timely streams, `replay` and `capture` respectively. At the same time, we have custom operators for `input` and `probe`, which introduce in…
-
I just found a few interesting papers which I think are very relevant for achieving efficient dom updates without virtual dom:
> Maier, Ingo, and Martin Odersky. "Higher-order reactive programming …
-
It is relatively easy to change the frequency of updates in differential dataflows. You take any `(data, time, diff)` update, and round the `time` up to the next integral multiple of whatever frequenc…
-
After reading through the docs I'm a little unclear on what happens should a worker fail (process/thread dies, network partition, etc).
Main concerns:
- Does the library panic?
- If not how can I…
tarqd updated
4 years ago
-
Our diagnostic views such as `mz_records_per_dataflow_operator` join record counts from differential dataflow with operators from timely dataflow. However, we can hold on to an arrangement for longer …
-
Hi, @frankmcsherry,
I have set up timely as a long-time service to server queries. But the problem is that in timely all dataflows share the same computation resources, which will lead to a long exec…
-
Right now NOT IN statements use a cross join which is not very performant - lets change that to use an antijoin instead and add some tests to stress the new implementation
-
This is a fascinating project. I've been studying differential dataflow and specifically the core operators like iterate and arrange. I've also been trying to map out how it juxtaposes with reactive p…
-
I would like to understand where my differential program spends time. Is my best bet to just use a generic CPU profiler or is there some sort of API for this in timely/differential? Using a generic pr…
-
From discussion with @benesch it came up that in active-active land, it makes less sense for the timely workers to host their own logging for purposes of analysis. At least, we do not expect the logs …