Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
refset
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
241.
▲
by
refset
3y ago
> Windows hegemony :chefs-kiss:
242.
▲
by
refset
3y ago
I replied with this already to another sibling comment raising the same issue: > I think he simply meant that Java was marketed and therefore prospered as a counter to Microsoft's dominance more generally. i.e. ".NET" bein
243.
▲
by
refset
3y ago
Assuming current multi-tenant infrastructure trends continue, over-provisioning of RAM and slow start up times are likely the much bigger efficiency issues.
244.
▲
by
refset
3y ago
I think he simply meant that Java was marketed and therefore prospered as a counter to Microsoft's dominance more generally. You're right that .Net (and the CLR) came later in the story ...as a counter to Java.
245.
▲
by
refset
3y ago
Thanks for the pointer :) it seems there's a follow-up to that paper in turn, with an explicit focus on that eviction strategy: "Write-Aware Timestamp Tracking" https://www.vldb.org/pvldb/vol16/p3323
246.
▲
by
refset
3y ago
In a similar vein, there's a neat "Efficient Page Replacement" strategy described in a LeanStore paper [0] that combines random selection with FIFO: > Instead of tracking frequently accessed pages in order to avoid evictin
247.
▲
by
refset
3y ago
> Do people really write recursive queries in the wild (non-recursive Datalog doesn’t count)? I believe a lot of RDF systems demand fast, recursive inferencing. This might be helpful context: https://docs.oxfordsemantic.tech&#
248.
▲
by
refset
3y ago
I asked Rich about his thoughts on query optimizers last year (not in the context of Datomic specifically) and his only reservation was around the practical implications for the operational experience. Specifically, that database systems sh
249.
▲
by
refset
3y ago
Datalog can be very effective for expressing certain kinds of problems and for generating efficient solutions to those problems. Particularly anything that is even mildly recursive, and therefore especially "knowledge graphs" that
250.
▲
by
refset
3y ago
> Datomic has a notion of rules which are mostly syntax sugar and do not support this sort of recursive reasoning. > Why is that a big deal? When rules are run automatically, you can build live, reactive systems, not just a database t
251.
▲
by
refset
3y ago
For comparison, I previously translated that cart parts scheduling example on the Flix homepage to Datomic-style Datalog syntax: https://gist.github.com/refset/21b3fc1dec9a6928943073809e133...
252.
▲
by
refset
3y ago
RDFox offers a rather impressive sounding Datalog inferencing engine: https://www.oxfordsemantic.tech/rdfox > We present a novel approach to parallel materialisation (i.e., fixpoint computation) of datalog programs in ce
253.
▲
by
refset
3y ago
That's awesome! Ram Dass has been a real hero for me. I also love how excerpts from Watts and Ram Dass have been picked up by so many (very talented) musicians over recent years, e.g. https://www.youtube.com/watch?v=nwT
254.
▲
by
refset
3y ago
The narrative here is that the evolution of database systems has always been in response to a rapidly changing landscape of "constraints", e.g. - The challenge of open R&D collaboration -> Postgres & MySQL - The ineffec
255.
▲
Constraint-Driven Innovation [pdf]
(mvdirona.com)
4 points
by
refset
3y ago
|
2 comments
256.
▲
by
refset
3y ago
> Why do you not trust Ventoy? > Ventoy is a great tool from what I’ve seen online and the use case it fills does save time and resources. However, I have some reservations about it. If I had to compromise a bunch of critical systems
257.
▲
Rubik – An Experiment in Geometry
(vraid.github.io)
3 points
by
refset
3y ago
|
1 comments
258.
▲
by
refset
3y ago
Ah I was thinking about running-on, but compiling-for is probably relevant also :) > I don't know if FPGAs would have an advantage over GPUs, since the bottleneck is often memory bandwidth and from a quick search it seems FPGAs are
259.
▲
by
refset
3y ago
Thank you for the link! That's a very interesting overview. Do you think the commodification of FPGAs could add another angle of interest/motivation here? Or is that hardware model likely to be incompatible with how these compilat
260.
▲
by
refset
3y ago
It's not a public facing product, but there was a talk from a team at Alibaba a couple of months ago during CMU's "ML⇄DB Seminar Series" [0] on how they augmented their NL2SQL transformer model with "Semantics Corre
261.
▲
by
refset
3y ago
I'm far from an expert on such things, but Co-dfns appears to be genuinely cutting edge research that could have utility for many language ecosystems (or do you disagree that this direction of GPU-based compilation holds promise?). If
262.
▲
by
refset
3y ago
Nothing has ever convinced me about the potential for array languages in practice quite like watching Aaron Hsu describe how he develops his parallel APL compiler [0] using two Notepad.exe windows side-by-side: https://www.youtub
263.
▲
Glommio, a Thread-per-Core Crate for Rust and Linux (2020)
(datadoghq.com)
3 points
by
refset
3y ago
|
0 comments
264.
▲
by
refset
3y ago
This post on Glommio is insightful - "Glommio is a cooperative thread-per-core crate for Rust & Linux based on io_uring": https://www.datadoghq.com/blog/engineering/introducing-glomm... The key insig
265.
▲
by
refset
3y ago
"YugabyteDB Anywhere" is open core though right? Half the value & complexity is in the orchestration stack. It's definitely a step forward, but such licensing is likely still too restrictive to ever supplant Postgres itse
266.
▲
by
refset
3y ago
If Postgres was already horizontally scalable and supported incrementally maintained recursive CTEs (like Materialize can do) then I could see how Rama would be mostly uninteresting to a seasoned SQL developer, but as it is I think Rama is
267.
▲
by
refset
3y ago
I can imagine Codd saying the exact inverse: any sufficiently complex data model quickly becomes intractable for developers to assemble ideal indexes and algorithms together each time in response to new queries, which kills productivity and
268.
▲
by
refset
3y ago
> If all business happens in one transactional system, your semantics are dramatically simplified. 100% agreed. One of the biggest issues SQL databases have faced is that the scope & scale of "one transactional system" has
269.
▲
by
refset
3y ago
Maybe https://plato.stanford.edu/entries/relations/
270.
▲
by
refset
3y ago
Operational Transform (an approach that requires a central server to coordinate edits)
More ›