Curtis, my top source of scoops, pointed me to this breathless review of Sun's new transactional memory hardware, making bold predictions that Sun will -- and I quote: "horsefuck the database world".
But unless I'm really missing something, how does this help? A database's bottleneck is not thread synchronization, it's atomic writing to disk. Sure, transaction management of in-memory data is costly. But not nearly as costly as writing updates to disk in an infallible manner.
Maybe there are specific database scenarios that really benefit from this. But a read-heavy scenario doesn't have a lot of transactional overhead, and a write-heavy scenario will be bound by disk write performance.
So again, where does this help? I must be totally missing something. Can you help steer me straight?
-david barrett
How does transactional memory improve disk commits?
Labels:
Coding
-
Jan 2014 (1) -
Mar 2012 (1) -
Nov 2011 (1) -
Oct 2011 (1) -
Apr 2011 (1) -
Mar 2011 (3) -
Feb 2011 (2) -
Jan 2011 (9) -
Nov 2010 (1) -
May 2010 (1) -
Mar 2010 (1) -
Feb 2010 (1) -
Jan 2010 (1) -
Dec 2009 (1) -
Nov 2009 (1) -
Oct 2009 (1) -
Sep 2009 (1) -
Aug 2009 (2) -
Jul 2009 (1) -
Jun 2009 (4) -
May 2009 (3) -
Apr 2009 (3) -
Mar 2009 (10) -
Feb 2009 (5) -
Jan 2009 (3) -
Dec 2008 (5) -
Nov 2008 (5) -
Oct 2008 (5) -
Sep 2008 (4) -
Aug 2008 (5) -
Jul 2008 (11) -
Jun 2008 (8) -
Feb 2008 (1) -
Aug 2007 (1) -
No comments:
Post a Comment