71–80 of 118 posts
Earlier quoted context omitted.
I'm not sure why it would need to be "disclosed", other than to suggest the author knows what they're talking about due to "domain knowledge".
Maybe because I don’t trust someone who allegedly writes databases but is proud about not knowing python.
Earlier quoted context omitted.
I'm not sure why it would need to be "disclosed", other than to suggest the author knows what they're talking about due to "domain knowledge".
Maybe because I don’t trust someone who allegedly writes databases but is proud about not knowing python.
It could be argued that it isn't really a benchmark unless you can accurately calculate the result based off of a common fundamental benchmark.
my feeling is that graph databases face an uphill battle for mass adoption not because their architects or vendors doing anything wrong but some intrinsic aspects of information exchange in most current situations and use cases * information tends to be private and/or commercially sensitive, this severs the links that graph dbs are good at representing (and made the "node focused" SQL approach the ubiquitous model th…
I saw very niche use cases 10 years ago but have seen more and more common use cases recently. Knowledge Graphs in particular have a lot of use. I’d expect to continue to see explosive growth in graph over the next 10 years.
As ubiquitous as SQL or document databases? Probably not. But very likely more and more use cases will be uncovered.
Earlier quoted context omitted.
It was... > It looks like Neo4j is faster than Memgraph in the Aggregate queries by about 3 times. Memgraph is faster than Neo4j for the queries they selected by about 2-3x except... Unless that's meant to be a joke? Maybe they were dunking on the "bullshit" benchmark with a worse comparison.
Oh, then I'm not sure what you mean. That line makes sense - the final benchmarks were performed on the author's machine. That's where the conclusion comes from. In theory, the spread between two benchmarked programs is not going to be hugely different between machines unless one is taking advantage of the hardware of one of the machines where the other doesn't (e.g. new syscall mechanisms such as io_uring, SIMD supp…
No, the author didn't run any benchmarks for Memgraph AFAICT, only for Neo4j. The numbers for mempgraph at the end are from the old benchmark, so on the old hardware.
Earlier quoted context omitted.
Maybe because I don’t trust someone who allegedly writes databases but is proud about not knowing python.
Who in their right mind would implement a database engine in Python?
Unfortuantely, an article that overstates benefits without any caveats is not illegal so it will carry on.
Many of us would like disclaimer e.g. "I work for the company" but also a much more bounded discussion, "this performance test works for this particular scenario" and perhaps "Please note, your scenario might be very different" and especially "Please contact me if you think I have missed something out".
I have worked for a business where you felt compelled to amplify the good and not talk about the bad but the world keeps spinning...
Earlier quoted context omitted.
Maybe because I don’t trust someone who allegedly writes databases but is proud about not knowing python.
Who in their right mind would implement a database engine in Python?