InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Microsoft Research's Accelerator: A Data-Parallel Library for .NET that Targets GPUs

Posted by Jonathan Allen on Jul 25, 2007

Sections
Development,
Architecture & Design
Topics
Research ,
Performance & Scalability ,
.NET
Tags
Parallel Programming

Microsoft Research's Accelerator Project exposes a .NET library for performing parallel data processing using a computer's GPU.

Accelerator is a .NET 2.0 DLL that requires DirectX 9, included with Windows XP SP2, and a graphics card that supports Pixel Shader 2.0 or above. Graphics cards without hardware vertex processing, common on cheaper laptops, do not appear to work.

Accelerator is released under a non-commercial Shared Source license agreement. This means that while a developer can look at the source code, special permission is needed to actually use it in a production environment. Also, the source is not actually included in the installer or on the project's wiki page.

The current build can be downloaded from Microsoft Research. Note that the date on this page is incorrect. The build you get was actually uploaded in July of this year. 







RelatedVendorContent

Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing

Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL

Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat

Monitor your Production Java App - includes JMX! Low Overhead - Free download

Cloud Access 360 Overview

No comments

Watch Thread Reply

Educational Content

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.

Cool Code

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.

Collaboration: At the Extremities of Extreme

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.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

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.

10 tips on how to prevent business value risk

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

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.