benwilson-512

7 ms·

1.
by benwilson-512 1y ago
We have been doing exactly this at CargoSense! We have gotten very far on just Postgres but as our BI and other analytics queries have gotten more complex and our scale of “business tables” grown 20x over the last 18 months it just wasn’t
2.
by benwilson-512 3y ago
My wife works as an acoustical consultant at a global construction firm. The things you hear about factories, offices, and even hospitals is wild. Don’t get me wrong the construction world works very hard to avoid issues but I think we in s
3.
by benwilson-512 3y ago
The processing unit in my espresso machine died and was back ordered for 4 months, so raspberry pi to the rescue! Is that much processing power necessary? Not even a little, but hey now it hosts its own web UI (local network only). Firmware
4.
by benwilson-512 3y ago
Hey folks! Author of Absinthe here, feel free to ask me any questions.
5.
by benwilson-512 3y ago
Hey vryotek, short version: stickiness is not necessary or important. It does use a websocket. To elaborate a bit, while each LiveView client is indeed associated with a long lived process in the LiveView server, the Phoenix framework provi
6.
by benwilson-512 4y ago
That's very cool. Presumably as well this could be opt out if you had specific operations (perhaps from a write-only API) that don't need to wait to do further writes?
7.
by benwilson-512 4y ago
In field metering situations you can have the timeline of each meter, when it records data points, and then you have the different timeline of the backend service, when it actually _receives_ data points. Bonus points if the meters can send
8.
by benwilson-512 4y ago
ARM support for the JIT is a great addition for any of us on an M1! I believe on Intel the JIT was improving compile times by 30-50%.
9.
by benwilson-512 5y ago
In practice we've seen it actually improve performance, because when fetching a data range for a device fewer actual rows have to be fetched from the disk. You pick certain columns (like device ID) that remain uncompressed and indexed
10.
by benwilson-512 5y ago
We've got a few billion rows in TSDB, pretty happy with it so far. Our workload fits the OLTP workflow more than OLAP though, we're processing / analyzing individual data points from IoT devices as they come in, and then prov
11.
by benwilson-512 5y ago
I recently installed two MrCool DIY minisplits which worked out great. They come with pre-charged quick connect coolant lines so you can install them without the need for flushing coolant or soldering the lines. If you're comfortable p
12.
by benwilson-512 5y ago
> Specially now we are using all the hotwire stuff. Maybe I'm missing something, but doesn't this have precisely the same latency characteristics as live view? I do agree that some of the "you don't need redis" a
13.
by benwilson-512 6y ago
The most immediate impact I'm noticing locally is a ~25-30% improvement in compile times from the JIT, which is always a delightful find in any release. Synthetic benchmarks of the Elixir GraphQL implementation show a 64% improvement!
14.
by benwilson-512 6y ago
And even if you're young, if you find yourself waking up at night with your heart racing, excessive snoring, etc, get it checked out. I got a CPAP machine at 20, and it's hard to overstate the impact. You can even just straight up
15.
Trackmytemp.org(trackmytemp.org)
1 points by benwilson-512 7y ago|0 comments
16.
by benwilson-512 7y ago
This looks very cool. Is there a story for managing users associated with AWS IAM roles or users?
17.
by benwilson-512 7y ago
Hey! We're looking to evaluate TimescaleDB for a logistics IoT scenario. Some of the data that enters our system comes from connected devices where recorded_at and inserted_at columns are basically the same. Some data however is source
18.
by benwilson-512 7y ago
Hey Erik, thanks for the post. In this vision, would this cluster of servers be reserved exclusively for timeseries data, or do you imagine it containing other ordinary tables as well? We're using postgres presently for some IoT, B2B a
19.
by benwilson-512 7y ago
We've also felt the complexity of React and Apollo. It works best when, as others mentioned, you've got distinct teams that can focus on each part. In situations where that isn't the case the same decouplings that make it eas
20.
by benwilson-512 7y ago
> "I've only done something as a hobby so I'm not qualified to do it professionally" Definitely don't let this hold you back. As long as you're up front about where you are, and are willing to learn, lack of
21.
by benwilson-512 7y ago
Hey folks! Co-Author of Absinthe here, happy to answer any questions about it. The post here is good, although these days we recommend using Dataloader vs Absinthe.Ecto. Dataloader really extends the idea behind Absinthe.Ecto while providin
22.
by benwilson-512 8y ago
A lot of folks are failing to read the article. They're intentionally holding each connection open for 1 whole second. This is a whole different ballgame than benchmarks where each connection is allowed to terminate as rapidly as it ca
23.
by benwilson-512 8y ago
In Erlang (and presumably Go) green threads end up in a waiting queue when waiting on further work to do, and as such don't need to be polled or consume any CPU at all while idle. It's only when they receive a message indicating m
24.
by benwilson-512 9y ago
<citation needed>
25.
by benwilson-512 9y ago
These notes definitely seem like a useful reference, although I wish the author spoke more about what it was they were trying to accomplish. As someone with only a cursory familiarity with Lasp I've been hoping to see some applications
26.
by benwilson-512 9y ago
Hey! Good questions. A) Absinthe 1.4 provides first class support for GraphQL Subscriptions, which give you the ability to push data to clients based on subscription documents they submit, triggered by events within the system. GraphQL Muta
27.
by benwilson-512 9y ago
The Github page may not be of much interest unless you're trying to get started, so let me say a couple words about our subscription implementation that's in the 1.4 release candidate. The idea with GraphQL subscriptions is that a
28.
by benwilson-512 9y ago
Sorry to hear it's a bother to you. The Scala implementation of GraphQL is called Sangria, so we thought we'd continue the theme. It also has the perk of providing some fun design opportunities.
29.
by benwilson-512 9y ago
Thanks! Stay tuned for for a deluge of new guide content: https://github.com/absinthe-graphql/absinthe/pull/416 We've been super busy getting the book finished but we want to make sure that we've al
30.
by benwilson-512 9y ago
Hey folks! I’m one of the Absinthe co authors, happy to answer any questions! We’re hoping to get the 1.4 release out soon, it’s was delayed a bit to make sure some features were in place for the book. For now though the 1.4.0–rc is availab

More ›