jsteemann

8 ms·

31.
by jsteemann 9y ago
Nice idea, I would take part in something like that too. By the way, there seems to be a raffle of free T-shirts (quite biased, as there's only the ArangoDB logo on them) in exchange for taking part in a survey: https://aran
32.
by jsteemann 9y ago
I think it's definitely reasonable to tune important production databases. But for many people databases have become commodity applications that they install and then forget. So even in reality not all installments will be properly tun
33.
by jsteemann 9y ago
Sure. Looking forward to see some follow-up post from you guys!
34.
by jsteemann 9y ago
Have you already received any feedback from clients about the performance impacts they observed due to the Spectre & Meltdown-related fixes? Would really be nice to see some figures for different kinds of applications.
35.
by jsteemann 9y ago
Given the potential slowdowns to be expected by the kernel fixes, I am not expecting a jolly January. I work for a database vendor.
36.
by jsteemann 9y ago
Yep, seems to me they put much work into the statement "the exploits do not have the potential to corrupt, modify or delete data.". Which leaves open if (that?) reading of data is possible. And as this is not explicitly denied, we
37.
by jsteemann 9y ago
Recent versions of several Linux distributions and FreeBSD have made newer clang and g++ versions available, which both have decent support for C++17 features. For example, Ubuntu 17.10 provides clang-5.0-3 and g++ 7.2.0. Installing clang 5
38.
by jsteemann 9y ago
It's kind of a problem if the compile/build step takes rather long. Then you want to avoid having any additional non-compiling revision to check when bisecting. But I agree in general, if the compile/build turn-around times a
39.
by jsteemann 9y ago
One mitigation for this is to use `col -bp` as a git pager, but it seems clumsy. However, for completeness I post it here with an example for how this makes the backdoor visible. Reproduce instruction: # clone repo and cd into it git clone
40.
by jsteemann 9y ago
Non-compiling commits make bisecting harder, when the goal is to find the commit that broke the build or a specific test. IMHO having to skip over non-compiling merge commits only makes bisecting take more time, and it may also "pollut
41.
by jsteemann 9y ago
Just to let you know: Google+ link on webpage is not doing anything, as it simply links to "#".
42.
by jsteemann 9y ago
Potentially unsafe optimizations, undefined behavior and random crashes that are hard to reproduce are normally nothing one wants to have in production builds. It's nice that UBSan will detect the problem at runtime, but that requires
43.
by jsteemann 9y ago
A "tiny" (read: small) C compiler can also be found at: https://bellard.org/tcc/ It has been unmaintained for a while now, but it's still good as a starting point. Interestingly enough it's a spin-o
44.
by jsteemann 9y ago
I remember reading Jack Crenshaw's "let's build a compiler" tutorial in the 90's. Though pretty outdated, I can definitely recommend it to everyone interested in compiler construction, because it's written from
45.
by jsteemann 9y ago
Nice article and a good read! Just came in and read part 2, so please don't blame me if the following has been posted in a comment for part 1 already. IMHO there are plenty of good books on compiler construction. One of the best ones I
46.
by jsteemann 10y ago
Can also use the movie database example graph made famous by Neo4J. I have adapted it for use in ArangoDB: https://github.com/jsteemann/movie-database
47.
by jsteemann 10y ago
Interesting finding. Do you have any further info on why it was slow, and on which platforms? thx!
48.
by jsteemann 10y ago
There isn't yet any benchmark result for this from ArangoDB. However, we already adjusted our Java driver to use VelocyPack instead of JSON internally and VelocyStream for the client-server communication. This has led to quite some per
49.
by jsteemann 10y ago
New graph viewer and AQL editor in 3.1 are really good IMHO.
50.
by jsteemann 11y ago
Very interesting! Would like to see a comparison with relational datastores (e.g. Postgres), too.
51.
by jsteemann 13y ago
In networks there'll always be failures. So I think it's still necessary to deal with the problem of your distributed database becoming partly disconnected and partition. And as long as there is consistency (though eventual) in ca
52.
by jsteemann 13y ago
Yes, AQL was inspired by XQuery. I think SQL is really good for querying relational databases. Actually we started with implementing something like SQL's SELECT clause in the very beginning of ArangoDB. The rationale was: "why inv
53.
by jsteemann 13y ago
the stuff was initially named AvocadoDB, but we have to rename last year because someone else claimed the same name (for whatever reason)
54.
by jsteemann 13y ago
Oh, he's so good...! And I say that coming from Cologne. You need to know the local club really dislikes Arango's current club (based 50 km away from here).
55.
by jsteemann 13y ago
As in many databases, ArangoDB allows some choices regarding durability. Immediate disk synchronisation is turned off by default in ArangoDB. Synchronisation is then performed by a background thread, which is frequently executing syncs. B
56.
by jsteemann 13y ago
To name just a few: - being relaxed about schemas: no more long-running ALTER TABLE commands, no more up-front schema definitions that waste time when doing proof-of-concepts etc. - being friendly to variable and hierarchical data: no more
57.
by jsteemann 13y ago
thanks for the great post! btw would it be possible to add the application directory to the article for download? saves at least a bit of typing. re the naming of databases & collections: this is indeed a good question! You may want to