Subject: General Tech, Processors, Mobile | February 18, 2012 - 09:06 PM | Scott Michaud
Tagged: Intel, mobile, developer
Clay Breshears over at Intel posted about lazy software optimization over on the Intel Software Blog. His post is a spiritual resurrection of the over seven year’s old article by Herb Sutter, “The Free Lunch is Over: A Fundamental Turn Toward Concurrency in Software.” The content is very similar, but the problem is quite different.
The original 2004 article urged developers to heed the calls for the multi-core choo choo express and not hang around on the single core platform (train or computing) waiting for performance to get better. The current article takes that same mentality and applies it to power efficiency. Rather than waiting for hardware that has appropriate power efficiency for your application, learn techniques to bring your application into your desired power requirements.
"I believe your program is a little... processor heavy."
The meat of the article focuses on the development of mobile applications and the concerns that developers should have with battery conservation. Of course there is something to be said about Intel promoting mobile power efficiency. While developers could definitely increase the efficiency of their code, there is still a whole buffet of potential on the hardware side.
If you are a developer, particularly of mobile or laptop applications, Intel has an education portal for best power efficiency practices on their website. Be sure to check it out and pick up the tab once in a while, okay?
Subject: Processors | May 12, 2011 - 08:21 AM | John Davis
Tagged: software, sdk, linux, Intel, developer
Intel has just released an update to their OpenCL (Open Computing Language) SDK (Software Development Kit). With this update Intel has released a 64bit .rpm package, and previously only supported Windows. OpenCL is a huge jump in the future of heterogeneous computing, and the future of computers. Intel joins a host of manufacturers that now support OpenCL which includes AMD/ATI and nVidia.
OpenCL has many competitors in the heterogeneous computing realm which includes nVidia's CUDA and Microsoft's DirectCompute. All of this is one giant step forward in GPGPU. In the majority of computers that have dedicated GPU's or have an Intel processor with on-cpu graphics that are not in use, this is great news! Hopefully, future Linux distributions implement OpenCL similar to OS X did with Snow Leopard.
Subject: General Tech, Graphics Cards, Storage | May 11, 2011 - 07:58 PM | Scott Michaud
Tagged: SQL, developer, CUDA
Programmers are beginning to understand and be ever more comfortable with the uses of GPUs in their applications. Late last week we explored the KGPU project. KGPU is designed to allow the Linux kernel to offload massively parallel processes to the GPU to offload the CPU as well as directly increase performance. KGPU showed that in terms of an encrypted file system you can see whole multiple increases in read and write bandwidth on an SSD. Perhaps this little GPU thing can be useful for more? Alenka Project thinks so: they are currently working on a CUDA-based SQL-like language for data processing.
CUDA woulda shoulda... and did.
SQL databases are some of the most common methods to store and manipulate larger sets of data. If you have a blog it almost definitely is storing its information in a SQL database. If you play an MMO your data is almost definitely stored and accessed on a SQL server. As your data size expands and your number of concurrent accesses increases you can see why using a GPU could keep your application running much smoother.
Alenka in its current release supports large data sets exceeding both GPU and system RAM via streaming chunks, processing, and moving on. Its supported primitive types are doubles, longs, and varchars. It is open source under the Apache license V2.0. Developers interested in using or assisting with the project can check out their Sourceforge. We should continue to see more and more GPU-based applications appear in the near future as problems such as these are finally lifted from the CPU and given to someone more suitable to bear.