ProductsServer Desktop & Workstation Developer Subscriptions Satellite OpenStack Platform For IBM POWER For SAP Business Applications Management For Scientific ComputingExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportA-MQ Accelerate Automate Integrate Application Platform BPM Suite BRMS JBoss community or Red Hat JBoss Middleware Data Grid Data Virtualization Developer Studio Portfolio Edition Fuse Fuse Service Works Operations Network Portal Web Framework Kit Web Server
SolutionsWhy Red Hat Why open hybrid cloud? The new IT Public cloud Cloud resource library Private cloud Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Cloud applications and workloadsSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release Red Hat JBoss Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum Red Hat JBoss Middleware development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingSOA and integration Business process management Custom Software Development Enterprise Data and Storage Systems management Migrations
SPICE: Simple Protocol for Independent Computing Environments
Providing a true PC-like experience with your virtualized desktops
What is SPICE?
SPICE is an open source, adaptive remote rendering protocol used by Red Hat® Enterprise Virtualization for Desktops to connect users to their virtual desktops. Unlike first-generation remote rendering protocols, such as Remote Desktop Protocol (RDP) and Independent Computing Architecture (ICA), SPICE features a multitiered architecture designed to support today's multimedia desktop experience.
SPICE functions on a 3-tier architecture, leveraging a unique component in each tier:
- SPICE Driver: A software component that resides within each virtual desktop
- SPICE Device: A software component that resides within the Red Hat Enterprise Virtualization Hypervisor
- SPICE Client: A software component that resides on the end-point device—either a thin client or a repurposed PC—used to access each virtual desktop
Efficient graphics processing
These three components work in tandem, determining the most efficient place to process graphics, in order to provide the best possible user experience, while reducing the system load.
If the client is powerful enough, SPICE sends the graphics commands to the client and processes them at the client level, significantly decreasing the load on the server. On the other hand, if the client is not powerful enough, SPICE processes the graphics at the host level, where graphics processing is a lot less expensive from a CPU perspective.
Get more information about SPICE—including whitepapers, manuals, and administration guides—or join the open source development community working on the SPICE protocol