seanlaff

6 ms·

1.
by seanlaff 1y ago
The ramdisk that overflows to a real disk is a cool concept that I didn't previously consider. Is this just clever use of bcache? If you have any docs about how this was set up I'd love to read them.
2.
by seanlaff 3y ago
Does duckdb support remote-duckdb as a storage engine? Seems like a way to support distributed duckdbs. Ducks all the way down? :)
3.
by seanlaff 3y ago
Oh! I understand, thanks for walking through that. Yes very terse compared to the equivalent react :)
4.
by seanlaff 3y ago
Ah ok! Very cool. Maybe I'm still missing a tiny piece of syntax? I don't see any output when I run that code in the fiddle https://jsfiddle.net/397fb684/
5.
by seanlaff 3y ago
Would we expect the list to re-render once the fetch finishes? This may just be years of react poisoning my brain const Stargazers = () => { const stargazers = van.state([]); fetch(`https://api.github.com&#x2F
6.
by seanlaff 3y ago
Hmm, maybe! Is that the idiomatic way to do async? I was thinking something along the lines of this, which react devs will have written a variation of plenty of times :) import { useEffect, useState } from "react"; cons
7.
by seanlaff 3y ago
This is cool, though I think a table-stakes example that is missing is how to do a network request. I see the stargazers example but that entire component is awaited, which doesn't mirror the common case of async fetch in response to u
8.
by seanlaff 3y ago
Ah yup, looks like @saurik pin-pointed my original source (iirc I slightly tweaked the jq, but you get the idea). Please do spread the idea- I would love capability native like this in gitlab.
9.
by seanlaff 3y ago
Im surprised there's still no "trace" view of pipeline execution, especially with how prevalent DAG pipelines have become. Somewhere on the internet I found this handy jq oneliner that will convert a pipeline into a format yo
10.
by seanlaff 4y ago
Is there more behind the scenes than just the `timestamp | json` table? From what I understand, any query in clickhouse against that involving a filter would require a full table scan
11.
by seanlaff 6y ago
Cities look so much more fun to explore when pedestrian-focused
12.
by seanlaff 6y ago
Many outlets gloss over the n+1 query problem, but I find it to be a major shortcoming of the gql spec. Sure there are solutions, but they are not very ergonomic. In one of our products we found simple requests blowing out to 100s of dow
13.
by seanlaff 6y ago
I’ve been curling this for years but was not aware of the new v2 api that shows hourly ascii charts. Looks sweet!
14.
by seanlaff 6y ago
Neat! How do you handle cross-geo latency? I know google has to rely on precise clocks to make this work in spanner
15.
by seanlaff 7y ago
This depends on row-based binlog replication, correct? Has netflix had to deal with systems with statement-based replication?
16.
by seanlaff 7y ago
Awesome!! It's been disheartening to see flotjs (which was essentially unmaintained for 5 years) still beat out scores of other charting libraries in terms of raw speed. Over the last few years we've tried a lot of different techn
17.
by seanlaff 7y ago
In the reference implementations of GQL, that “one query” from the client balloons out in to possible hundreds of queries out the back side of GQL. Things like dataloader exist but the behavior of your schema gets harder and harder to reaso
18.
by seanlaff 7y ago
` If Query Batching is enabled, Apollo will not issue requests immediately. Instead it will wait for up to 10 ms to see if more requests come in from other components. ` This has always felt pretty lame to me. GraphQL has the entire request
19.
by seanlaff 7y ago
Evan I think this is a great experiment. React hooks was an interesting idea and I like how Vue’s approach feels even more reactive (a la observable.com) There seems to be an overall trend towards more reactivity and I applaud Vue for takin
20.
by seanlaff 7y ago
The v8 isolates tech is super cool. It seems the other major providers might not be leveraging it in their FaaS platforms- do you have a hypothesis of why?
21.
by seanlaff 8y ago
I’d recommend taking a look at Vega https://vega.github.io/vega/ or its sibling Vega-lite. It exposes all of its configuration via declarative JSON. I could see it working well for a use case like this
22.
by seanlaff 8y ago
This datasource doesn't require any custom panels to function. To your point though, it would be nice if grafana supported incremental time range querying out of the box, since many backends don't support streaming data.
23.
by seanlaff 8y ago
Agreed, watching dashboards is no substitute for alerting. However, one of the motivators for doing this is to reduce pressure on the metric backend. It's common to have Grafana reports refresh at 5s intervals, which if you have sub-se
24.
Show HN: Grafana Live Streaming Datasource Implementation(github.com)
120 points by seanlaff 8y ago|13 comments