Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
thinkerlang
Home
+ new post
About this group
Join this group
Message from discussion Mnesia scales?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Joel Reymont  
View profile  
 More options Dec 10 2008, 11:21 am
From: Joel Reymont <joe...@gmail.com>
Date: Wed, 10 Dec 2008 16:21:49 +0000
Local: Wed, Dec 10 2008 11:21 am
Subject: Re: Mnesia scales?
Print | View thread | Show original | Report this message | Find messages by this author

On Dec 10, 2008, at 2:04 PM, grant michaels wrote:

> No offense taken, my erlang knowledge is more cerebral and less  
> practical thus far ... I have read a lot, but coded very little ...  
> I do remember, though, reading that the Dukes of Erl has addressed  
> the 2GB limit w/ success ...

I wrote (the initial?) implementation for the Dukes [1] and that  
implementation is inherently faulty, like any other attempt to add a  
new backend to Mnesia.

[1] http://www.wagerlabs.com/blog/2008/06/mnesia-unlimited.html#more

Yes, you do get to go past 2Gb by using Tokyo Cabinet [2] but the  
intractable issue is that any operation in the non-Mnesia backend runs  
outside of Mnesia transaction management.

http://sourceforge.net/projects/tokyocabinet/

Mnesia assumes that the transaction succeeded by the time the custom  
backend code is invoked to store the data in Tokyo Cabinet, S3, etc.  
and there's absolutely no way to report errors back to Mnesia at this  
point.

This is a fundamental issue that requires  a significant Mnesia  
rewrite to fix. Mnesia has to be made aware of the fact that it deals  
with table types other than ram_copies, disc_copies and  
disc_only_copies. I think that any rewrite of the scale needed here is  
unlikely to make it into OTP for fear of compromising Mnesia stability.

I may be wrong but I did what I did since it was relatively  
straightforward and fit within my client's budget.

--
http://wagerlabs.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google