> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/getting-started/uploading-content/patched-uploads/benchmarks.md).

# Benchmarks

## Specs

```
============================================================
BENCHMARK SYSTEM INFORMATION
============================================================

OS:               Windows 10.0.26200
CPU:              AMD64 Family 25 Model 8 Stepping 2, AuthenticAMD
Cores:            32 physical / 64 logical
RAM:              127.9 GB

Network:
  Download:       450Mbps
  Upload:         70Mpbs
```

{% hint style="info" %}
For the patched upload benchmarks, a single material color was changed. This represents a real change on the smaller side and so the results skew to best-case scenarios.
{% endhint %}

## Badger

### Project size

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (shipping) | 6                 |
| Mac Client (shipping)     | 8.9               |
| Linux Client              | 5.7               |
| Linux Server              | 1.2               |
| iOS Client                | 4.8               |
| Total                     | 26.6              |

### Results

All base patches perform a full cook similarly to the legacy non-patching case

| Scenario            | Cook  | Package | Upload | Total   |
| ------------------- | ----- | ------- | ------ | ------- |
| No patching         | 11:27 | 5:21    | 54:50  | 1:11:38 |
| Base patch (no RCC) | 11:08 | 5:37    | 52:28  | 1:09:13 |
| Base patch (RCC)    | 11:34 | 5:32    | 52:37  | 1:09:43 |

Patched upload without RCC performs the optimization during the upload step. The same assets are cooked and packaged as in the legacy case. Assets that have not changed are then discarded before the upload

{% hint style="success" %}
Patched upload without RCC resulted in a <mark style="color:$success;">**\~70%**</mark> reduction of the total cook & upload time and a <mark style="color:$success;">**\~94%**</mark> reduction in the content size that a user would need to download to get this updated content
{% endhint %}

| Scenario                | Cook  | Package | Upload | Total |
| ----------------------- | ----- | ------- | ------ | ----- |
| Patched upload (no RCC) | 11:21 | 5:48    | 3:29   | 20:38 |

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (Shipping) | 0.38              |
| Mac Client (Shipping)     | 0.38              |
| Linux Client (Shipping)   | 0.38              |
| Linux Server (Shipping)   | 0.02              |
| Ios Client (Shipping)     | 0.38              |
| Total                     | 1.54              |

Patched upload with RCC performs the optimization during the cook step. Assets are instead discarded from the cook which reduces the amount of assets being packaged and uploaded as a result

{% hint style="success" %}
Patched upload with RCC resulted in a <mark style="color:$success;">**\~97%**</mark> reduction of the total cook & upload time and a <mark style="color:$success;">**\~99%**</mark> reduction in the content size that a user would need to download to get this updated content
{% endhint %}

| Scenario             | Cook | Package | Upload | Total |
| -------------------- | ---- | ------- | ------ | ----- |
| Patched upload (RCC) | 1:19 | 0:14    | 0:27   | 2:00  |

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (Shipping) | 0.01              |
| Mac Client (Shipping)     | 0.02              |
| Linux Client (Shipping)   | 0.01              |
| Linux Server (Shipping)   | 0.01              |
| Ios Client (Shipping)     | 0.01              |
| Total                     | 0.06              |

## ODK

### Project size

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (Shipping) | 0.71              |
| Mac Client (Shipping)     | 1.3               |
| Linux Client (Shipping)   | 0.72              |
| Linux Server (Shipping)   | 0.1               |
| Total                     | 2.83              |

### Results

All base patches perform a full cook similarly to the legacy non-patching case

| Scenario            | Cook | Package | Upload | Total |
| ------------------- | ---- | ------- | ------ | ----- |
| No patching         | 1:29 | 0:44    | 5:40   | 7:53  |
| Base patch (No RCC) | 1:46 | 0:20    | 5:20   | 7:26  |
| Base patch (RCC)    | 1:41 | 0:16    | 5:20   | 7:17  |

Patched upload without RCC performs the optimization during the upload step. The same assets are cooked and packaged as in the legacy case. Assets that have not changed are then discarded before the upload

{% hint style="success" %}
Patched upload without RCC resulted in a <mark style="color:$success;">**\~62%**</mark> reduction of the total cook & upload time and a <mark style="color:$success;">**\~99%**</mark> reduction in the content size that a user would need to download to get this updated content
{% endhint %}

| Scenario                | Cook | Package | Upload | Total |
| ----------------------- | ---- | ------- | ------ | ----- |
| Patched upload (no RCC) | 2:20 | 0:16    | 0:14   | 2:50  |

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (Shipping) | 0.006             |
| Mac Client (Shipping)     | 0.007             |
| Linux Client (Shipping)   | 0.006             |
| Linux Server (Shipping)   | 0.005             |
| Total                     | 0.02              |

Patched upload with RCC performs the optimization during the cook step. Assets are instead discarded from the cook which reduces the amount of assets being packaged and uploaded as a result

{% hint style="success" %}
Patched upload with RCC resulted in a <mark style="color:$success;">**\~86%**</mark> reduction of the total cook & upload time and a <mark style="color:$success;">**99.6%**</mark> reduction in the content size that a user would need to download to get this updated content
{% endhint %}

| Scenario             | Cook | Package | Upload | Total |
| -------------------- | ---- | ------- | ------ | ----- |
| Patched upload (RCC) | 0:43 | 0:07    | 0:11   | 1:01  |

| Platform                  | Content Size (GB) |
| ------------------------- | ----------------- |
| Windows Client (Shipping) | 0.003             |
| Mac Client (Shipping)     | 0.003             |
| Linux Client (Shipping)   | 0.003             |
| Linux Server (Shipping)   | 0.002             |
| Total                     | 0.01              |

## Summary

### Upload Time

| Project | No RCC (% reduction in time) | RCC (% reduction in time) |
| ------- | ---------------------------- | ------------------------- |
| Badger  | 70%                          | 62%                       |
| ODK     | 97%                          | 86%                       |

This table summarizes the cook & upload time improvements when using RCC and not using RCC (benefit for content creators)

### Content Size

#### Badger

| Platform      | Full Upload  | Patched (no RCC) | Patched (RCC) |
| ------------- | ------------ | ---------------- | ------------- |
| windowsclient | 6.01 GB      | 0.38 GB          | 0.01 GB       |
| macclient     | 8.89 GB      | 0.38 GB          | 0.02 GB       |
| linuxclient   | 5.67 GB      | 0.38 GB          | 0.01 GB       |
| linuxserver   | 1.15 GB      | 0.02 GB          | 0.01 GB       |
| iosclient     | 4.80 GB      | 0.38 GB          | 0.01 GB       |
| **Total**     | **26.52 GB** | **1.54 GB**      | **0.06 GB**   |

* Patched (no RCC): **94% reduction** from full upload
* Patched (RCC): **99% reduction** from full upload

### Content Size

#### ODK

| Platform      | Full Upload | Patched (no RCC) | Patched (RCC) |
| ------------- | ----------- | ---------------- | ------------- |
| windowsclient | 0.69 GB     | 0.006 GB         | 0.003 GB      |
| macclient     | 1.19 GB     | 0.007 GB         | 0.003 GB      |
| linuxclient   | 0.67 GB     | 0.006 GB         | 0.003 GB      |
| linuxserver   | 0.09 GB     | 0.005 GB         | 0.002 GB      |
| **Total**     | **2.65 GB** | **0.02 GB**      | **0.01 GB**   |

* Patched (no RCC): **99% reduction** from full upload
* Patched (RCC): **99.6% reduction** from full upload


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.otherside.xyz/platform-documentation/creation/unreal-development/getting-started/uploading-content/patched-uploads/benchmarks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.