Developer(s) | |
---|---|
Operating system | Android (operating system) |
Website | developer |
RenderScript is a component of the Android operating system for mobile devices that offers an API for acceleration that takes advantage of heterogeneous hardware. It allows developers to increase the performance of their applications at the cost of writing more complex (lower-level) code.
It provides the developer three primary tools: A simple 3D rendering API, a compute API similar to CUDA, and a C99-derived language.
History
RenderScript was added in Android 3.0 Honeycomb [1]
As of Android 4.1, Renderscipt's experimental 3D rendering API has been deprecated, and now exists solely as a compute API.
Android 4.2 added new capabilities to script intrinsics, such as Blend and Blur; as well as ScriptGroups which allow you to chain together related RenderScript scripts and execute them with one call.
Most recently, Google added FilterScript, which is a subset of RenderScript that allows developers to write their image processing operations in FilterScript using the standard RenderScript runtime API, but within stricter constraints that ensure wider compatibility and improved optimization across multi-core CPUs, GPUs, and DSPs. FilterScript is a less precise in terms of numeric datatype precision, and more cross device compatible subset of RenderScript – and should not be mistaken for a RenderScript replacement technology.[2]
Features
Portability
RenderScript is designed to always run on the various Android platforms regardless of hardware type. Performance tuning is done at runtime.
RenderScript portability depends upon device-specific drivers:[3] a basic CPU-only driver is provided for every device, while there exist some specific chipset-provided RenderScript drivers that enable GPU usage (e.g. Qualcomm specific drivers, which are provided in the libRSDriver_adreno.so
Android library).
Performance
RenderScript is designed to tune tasks at runtime that can be efficiently split and run concurrently on the underlying hardware.[4]
As of Android 4.2, RenderScript has been expanded to run on the GPU in addition to the CPU on supported systems.[5]
Limitations
- RenderScript cannot yet express on-chip inter-thread communication (known as local memory in OpenCL, and shared memory in CUDA).
- RenderScript cannot yet express hardware-implemented 2D and 3D lookups with bilinear interpolation (known as texture in CUDA, and image read in OpenCL).
References
- ^ https://developer.android.com/about/versions/android-3.0-highlights.html#graphics
- ^ "Android 4.2 APIs". Retrieved 2013-03-20.
- ^ Marchetti, Alberto (2016). RenderScript: parallel computing on Android, the easy way (1st ed.).
- ^ https://android-developers.googleblog.com/2011/03/renderscript.html
- ^ "Jelly Bean - Renderscipt Performance". Retrieved 2012-11-27.