Sign In
Cyrus' Blather
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
No tags have been created or used yet.
Archive
Archives
November 2005
(1)
October 2005
(2)
September 2005
(11)
August 2005
(3)
July 2005
(5)
June 2005
(17)
May 2005
(8)
April 2005
(36)
March 2005
(30)
February 2005
(5)
January 2005
(7)
December 2004
(4)
November 2004
(5)
October 2004
(6)
September 2004
(16)
August 2004
(25)
July 2004
(35)
June 2004
(77)
May 2004
(73)
SF/JavaOne, Day 4, Speculative Locking
MSDN Blogs
>
Cyrus' Blather
>
SF/JavaOne, Day 4, Speculative Locking
SF/JavaOne, Day 4, Speculative Locking
CyrusN
29 Jun 2005 7:14 PM
Comments
5
Extremely interesting talk today about making a highly scalable VM for java that can handle a high number of threads far better than the current VMs out there. What's better than that? It runs your code better without requiring you to change any of your code at all. How does it work? At a high level it allows the VM to actually run your synchronized code in parallel across all running threads, and you only pay a penalty if there would have been data contention between two threads. In the common case there will be no problem and your thread will execute the critical section *without* acquiring a lock. And if there is a conflict it can be detected with existing techniques, and standard transactional rollback methods can come to the rescue here. Apperantly this idea comes into play in databases and is used to allow scalable performance on machines with a high number of CPUs (like 128+). It sounds very interesting, but i'm extremely confused how it deals with those pesky issues maintaining atomicity or consistancy.
With their testing they've found that the can an amazing level of scaling where in previous systems you could hit a wall extremely quickly.
It's enormously interesting, and far too complicated to go into depth fully in this post. So if you want to read more google a bit. From that, i found this very interesting
paper
on the the topic.
5 Comments
Blog - Comment List MSDN TechNet
Comments
Loading...