1page.title=Computation 2page.landing=true 3page.landing.intro=RenderScript provides a platform-independent computation engine that operates at the native level. Use it to accelerate your apps that require extensive computational horsepower. 4page.landing.image= 5 6@jd:body 7 8<div class="landing-docs"> 9 10 <div> 11 <h3>Blog Articles</h3> 12 13 <a 14href="http://android-developers.blogspot.com/2013/01/evolution-of-renderscript-performance.html"> 15 <h4>Evolution of RenderScript Performance</h4> 16 <p>It’s been a year since the last blog post on RenderScript, and with the release 17 of Android 4.2, it’s a good time to talk about the performance work that we’ve done 18 since then. One of the major goals of this past year was to improve the performance 19 of common image-processing operations with RenderScript.</p> </a> 20 21 <a 22href="http://android-developers.blogspot.com/2012/01/levels-in-renderscript.html"> 23 <h4>Levels in RenderScript</h4> 24 <p>For ICS, RenderScript (RS) has been updated with several new features to simplify 25 adding compute acceleration to your application. RS is interesting for compute 26 acceleration when you have large buffers of data on which you need to do significant 27 processing. In this example we will look at applying a levels/saturation operation 28 on a bitmap.</p> 29 </a> 30 31 <a 32href="http://android-developers.blogspot.com/2011/03/renderscript.html"> 33 <h4>RenderScript Part 2</h4> 34 <p>In Introducing RenderScript I gave a brief overview of this technology. 35 In this post I’ll look at "compute" in more detail. In RenderScript we use 36 "compute" to mean offloading of data processing from Dalvik code to 37 RenderScript code which may run on the same or different processor(s).</p> 38 </a> 39 </div> 40 41 </div> 42</div>