Re: Lock-free databases

From: Joe Seigh <jseigh_01_at_xemaps.com>
Date: Tue, 08 Nov 2005 23:00:18 -0500
Message-ID: <r4mdnWBDc5K56ezenZ2dnUVZ_v6dnZ2d@comcast.com>

VC wrote:
> "Mark D Powell" <Mark.Powell_at_eds.com> wrote in message
> news:1131475590.080140.136430_at_g47g2000cwa.googlegroups.com...
>

>>Technically from the theories point of view what you say is true, but I
>>do not think you can create a db manager based on this concept that
>>works well in a high concurrent update environment.

>
>
> "ANTs 3.2 is also the only lock-free relational database management system
> architected for popular 64-bit Linux operating system implementations
> running on AMD Opteron and Intel Xeon platforms. The ANTs Data Server sets a
> new precedent in the database industry, allowing large OLTP, real-time
> analytical processing and enterprise reporting to run concurrently in the
> same server. "
>
> http://www.ants.com/index.php?option=com_content&task=view&id=437&Itemid=29

Saying you're lock free isn't the same as being lock-free. Unless their bottlenecks are IPC related, I don't see how their lock-free patented techniques would help performance.

>
> http://www.eweek.com/article2/0,1895,1845154,00.asp

This article seems to point to being an in memory database as the main factor in performance.

-- 
Joe Seigh

When you get lemons, you make lemonade.
When you get hardware, you make software. 

Received on Tue Nov 08 2005 - 22:00:18 CST