Since 1986

RTPatch Overview

Byte-Level Differencing

Platforms

Features

What's New

Specialized Editions:

RTPatch Server

RTPatch for Mac

RTPatch Embedded

Resources:

Pricing and Evaluation

Multi-core Support

RTPatch for Games

Examples of Use

RTPatch OEM

20 Years of RTPatch

RTPatch Server

RTPatch Server is a specialized edition of RTPatch intended for applications where scalability and resource consumption is critical. Powered by a unique, patented build algorithm, RTPatch Server provides many features not found in any other tool of its kind:

• RTPatch Server may be used in multiple simultaneous instances without adversely affecting the running operations of the system. Previous byte-level difference algorithms were designed to run as a single instance on a dedicated machine.
• Linear build time: The time to identify and encode the byte-level differences between files is linear with respect to input file sizes. Previous byte-level difference engines required quadratic runtimes.
• Sequential file access: RTPatch Server uses a single read pass during data comparison, with no backward seeks. Ideal for situations that involve costly seeks (tape media), or in cases where back-seeking is not possible (streaming), this file access approach is unlike any previous byte-level difference technology.
• Memory and other system resources are limited and definable. All of the resource requirements of RTPatch Server are independent of the sizes or numbers of files upon which it operates. In addition, the actual amount of various resources may be defined. As little as 32-64MB of RAM and no temporary disk space, is required for desktop/server operation. Smaller memory footprints are possible for patch creation on embedded systems.
• Memory is limited and chosen by the developer: Previous byte-level difference engines required memory equal to 1.5x the size of the old and new files combined. When the requirement exceeded available memory, a swap to disk or unrecoverable error would occur.
• Other resources: Previous byte-level difference engines required temporary disk space and swap file space. RTPatch Server requires none.
• Multi-core enabled: RTPatch Server uses a multi-threaded patch build approach, dividing the build operation for a single file pair into multiple tasks and assigning those tasks to available processors/cores. The number of cores used is configurable.