Lloyd R. Prentice
Wed Oct 14 05:19:56 CEST 2015
So if we dig into the code, what exactly needs to change to make that happen?
This is a great teachable moment where the wizards of Erlang can help us with less understanding significantly advance our Erlang skills--- if nothing else, guide us through the design decisions that shaped mnesia, the architecture, and the significant code passages that impose current limitations.
Why? To broaden the base of folks capable of extending and advancing the Erlang legacy.
All the best,
Sent from my iPad
> On Oct 13, 2015, at 9:16 PM, "Richard A. O'Keefe" <> wrote:
>> On 14/10/2015, at 6:46 am, <> <> wrote:
>> I asked Fred what it would it take to upgrade Mnesia for the 21st century (or, at least, for the next decade). He didn't know.
> There's one thing that strikes me.
> I could go to a shop today and buy a 1 TB external drive for
> NZD 75, including Goods and Services Tax of 15%. (At least
> that's what the ad I saw a couple of days ago said.)
> That's almost exactly USD 50. This is a drive that fits in
> a shirt pocket, with room left over for all sorts of junk.
> To make Mnesia a data base for the 2010s, it has to be able to
> handle at least 1TB of data. Heck, I've got enough goodies-for-
> research money left that I could get the department to buy me
> ten of these gadgets, so let's say Mnesia
> - should be able to handle a single table in the low TB
> - should be able to handle a collection of tables in the
> tens of TB
> - where "handle" includes creating, populating, checking,
> recovering, and accessing in "a reasonable time".
> That's a "single machine data base for the 2010s".
> Of course there are multicore, cluster, and network issues as
More information about the erlang-questions