lsuresh

7 ms·

1.
by lsuresh 1mo ago
We use self-hosted Github runners, but it's a moot point if all of Github is mostly down as is the case right now. :\
2.
by lsuresh 2mo ago
Isn't most of Rust's compilation overhead from the llvm backend?
3.
by lsuresh 2mo ago
Over at Feldera, we focus on IVM for SQL, but incremental computing problems show up far and wide: UIs, spreadsheets, control planes, compilers and more.
4.
by lsuresh 4mo ago
When I last used it for such use cases, it was better to decompose the problem into something incremental (so fixed placements become constants). Most of the latencies we saw were spent in the presolve phase which scaled with overall input
5.
by lsuresh 4mo ago
I'm a big fan of the CP-SAT solver. It was a remarkable piece of tech to learn about (especially Peter Stuckey's talks on lazy clause generation [1]). I'd used it in a past life to build a Kubernetes scheduler [2] and tackle
6.
by lsuresh 6mo ago
We built Feldera's engine in Rust: https://github.com/feldera/feldera
7.
by lsuresh 6mo ago
There are some solid ideas here and would definitely apply to the IVM engine we're building. I'm curious if some of these effects could play a role in faster rust compilation times (e.g. nopanic..)?
8.
by lsuresh 6mo ago
We use an in-product profiler (discussed here: https://www.feldera.com/blog/introducing-feldera's-visual-pr... ), along with CPU profiles to identify where in the code we're spending time.
9.
by lsuresh 6mo ago
Good questions! Feldera tries to be row- and column-oriented in the respective parts that matter. E.g. our LSM trees only store the set of columns that are needed, and we need to be able to pick up individual rows from within those columns
10.
by lsuresh 7mo ago
Feldera co-founder here. Great discussions here. Some folks pointed out that no one should design a SQL schema like this and I agree. We deal with large enterprise customers, and don't control the schemas that come our way. Trust me, w
11.
by lsuresh 7mo ago
Thanks for the Feldera shoutout Jim. For anyone else, if you want to try out Feldera and IVM for feature-engineering (it gives you perfect offline-online parity), you can start here: https://docs.feldera.com/use_cases/f
12.
Feldera's Visual Profiler(feldera.com)
3 points by lsuresh 8mo ago|0 comments
13.
by lsuresh 1y ago
Start with Postgres and scale later once you have a better idea of your access patterns. You will likely model your graph as entities and recursively walk the graph (most likely through your application). If the goal is to maintain views ov
14.
by lsuresh 1y ago
I currently run Firefox nightly with cross-site cookies disabled and all the trackers/scripts blocked. I also run uBlock Origin. Any idea if privacy badger is redundant with this set up?
15.
by lsuresh 1y ago
Thanks for the kind words (Feldera co-founder here). I'll pass it on to the design team. :)
16.
by lsuresh 1y ago
Do give us at Feldera a shot -- full IVM for arbitrary SQL + UDFs: https://github.com/feldera/feldera/
17.
by lsuresh 1y ago
Would love to have our team try this out (we have some ridiculous rust builds).
18.
by lsuresh 1y ago
Yeah that's been our biggest issue in this ecosystem (the non-JVM clients). They can't do writes and are often far behind on feature parity with the blessed JVM clients.
19.
by lsuresh 1y ago
Not the one you asked, but here's what I would have told my 17 year old self. * "Slope beats y-intercept." The best computer scientists and engineers I've ever worked with and/or mentored embodied this principle mor
20.
Iceberg, the right idea – the wrong spec – Part 2 of 2: The spec(database-doctor.com)
35 points by lsuresh 1y ago|8 comments
21.
by lsuresh 1y ago
It's the first time I'm hearing about the Berlin Declaration. :)
22.
by lsuresh 1y ago
This made my day. Thank you for the kind words! What were you working on?
23.
by lsuresh 1y ago
USENIX and their conferences were the absolute best to publish with. You as a researcher focus on submitting papers and/or being part of the PC. They help organize the whole conference instead of depending on an army of volunteers (you
24.
by lsuresh 1y ago
I first went to sqlx thinking it would be like JOOQ for Rust, but that wasn't the case. It's a pretty low-level library and didn't really abstract away the underlying DBs much, not to mention issues with type conversions. We&
25.
The Babel Tower of SQL Dialects(feldera.com)
4 points by lsuresh 1y ago|0 comments
26.
by lsuresh 1y ago
Not sure either. We added recursion to SQL in Feldera and it's Turing-complete: https://www.feldera.com/blog/recursive-sql-queries-in-felder...
27.
by lsuresh 1y ago
Thanks for the kind words. :) We hear you on the dialect differences. An interesting case of a user dealing with this problem: they use LLMs to mass migrate SparkSQL code over to Feldera (it's often json-related constructs as you also
28.
by lsuresh 1y ago
That's a cool demo you're building using ddlog! FWIW, we, the ddlog team have moved on to found Feldera ( https://github.com/feldera/feldera ). You could consider using DBSP directly through Rust.
29.
by lsuresh 1y ago
Was this for a release build or a debug build?
30.
by lsuresh 1y ago
Hard agree. Practically all the bottlenecks we run into with Rust compilation have to do with the LLVM passes. The frontend doesn't even come close. (e.g. https://www.feldera.com/blog/cutting-down-rust-compile-time

More ›