New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on May 04, 2010
Brahma is an open source C# library that provides support for parallel computations running on a variety of processors. Currently, Brahma has a GPU provider but its modular structure allows using different providers for other types of processors. One C# method can contain both statements running on CPU and GPU without additional glue code.
Brahma performs parallel computations by transforming LINQ statements into programs that run on the target processor. The program generated contains High Level Shading Language statements if it was targeted for DirectX or OpenGL Shading Language statements if it was targeted for OpenGL. For performance improvements LINQ queries are compiled once and used many times as necessary.
The following code multiplies the values in an array by 2 in parallel:
// Create the computation provider
var computationProvider = new ComputationProvider();
// Create a data-parallel array and fill it with data
var data = new DataParallelArray<float>(computationProvider,
new[] { 0f, 1f, 2f, 3f, 4f, 5f, 6f });
// Compile the query
CompiledQuery query = computationProvider.Compile<DataParallelArray<float>>
(
d => from value in d
select value * 2f
);
// Run the query on this data
IQueryable result = computationProvider.Run(query, data);
// Print out the results
foreach (float value in result)
Console.WriteLine(result[i]);
// Get rid of all the stuff we created
computationProvider.Dispose();
data.Dispose();
result.Dispose();
The source code and binaries are available under Eclipse Public License 1.0.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
SCM best practices for multiple processes, releases & distributed teams
Looks cool, but with this name it would be cool anyway: Brahma is a popular trademark here in Brazil and also a company within that group that brought Budweiser.
As per Hindu mythology, Brahma is the one who is the conciever / Creator of the Universe.
Thanks for sharing it, Sanket
I will search for some books about Hindu mythology. Beside being an interesting subject, I have another motivation: this year my sister married a guy from India.
I also will keep drinking beer from Brahma company ;)
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
3 comments
Watch Thread Reply