# Appendix D: Performance evaluation data

The detailed data for the performance evaluation is given tables below. In any table, each row shows the execution time (in second) of inserting a vector noise into a Blender scene whose name is given in the table name, and the time (also in second) of verifying the distortions regions on a frame rendered from the scene.

The tests are proceeded on a workstation of Intel:registered:Core:tm:i5 2.5 GHz CPU, 32 GB RAM. The noise insertion and noise verification do not need GPU.

#### Table 3: <a href="#tab_coca_cola_perf" id="tab_coca_cola_perf"></a>

|               |                |                   |
| ------------- | -------------- | ----------------- |
| Vector length | Insertion time | Verification time |
| 2             | 0.747          | 0.343             |
| 5             | 0.785          | 0.845             |
| 7             | 0.822          | 1.059             |
| 10            | 0.871          | 1.525             |
| 12            | 0.923          | 1.855             |
| 15            | 0.982          | 2.352             |
| 17            | 1.061          | 2.612             |
| 19            | 1.062          | 2.929             |
| 20            | 1.092          | 3.081             |
| 21            | 1.094          | 3.217             |
| 23            | 1.163          | 3.508             |
| 25            | 1.204          | 3.786             |
| 27            | 1.241          | 4.182             |
| 29            | 1.330          | 4.475             |
| 30            | 1.335          | 4.673             |
| 32            | 1.394          | 5.059             |
| 35            | 1.472          | 5.585             |
| 37            | 1.490          | 5.982             |
| 40            | 1.612          | 6.409             |

Coca-Cola

#### Table 4: <a href="#tab_grease_pencil_bike_perf" id="tab_grease_pencil_bike_perf"></a>

|               |                |                   |
| ------------- | -------------- | ----------------- |
| Vector length | Insertion time | Verification time |
| 2             | 0.920          | 0.477             |
| 5             | 1.300          | 1.077             |
| 7             | 1.524          | 1.412             |
| 10            | 2.085          | 1.976             |
| 12            | 2.239          | 2.286             |
| 15            | 2.550          | 2.722             |
| 17            | 2.865          | 3.068             |
| 19            | 3.153          | 3.453             |
| 20            | 3.269          | 3.527             |
| 21            | 3.439          | 3.747             |
| 23            | 3.592          | 4.123             |
| 25            | 3.975          | 4.546             |
| 27            | 4.279          | 4.913             |
| 29            | 4.594          | 5.313             |
| 30            | 4.666          | 5.557             |
| 32            | 5.087          | 5.812             |
| 35            | 5.434          | 6.265             |
| 37            | 5.729          | 6.654             |
| 40            | 6.229          | 7.116             |

Grease Pencil Bike scheme

#### Table 5: <a href="#tab_blender_35_splash" id="tab_blender_35_splash"></a>

|               |                |                   |
| ------------- | -------------- | ----------------- |
| Vector length | Insertion time | Verification time |
| 2             | 3.959          | 0.546             |
| 5             | 7.125          | 0.922             |
| 7             | 7.468          | 1.251             |
| 10            | 8.938          | 1.642             |
| 12            | 9.934          | 1.871             |
| 15            | 12.773         | 2.443             |
| 17            | 13.721         | 2.751             |
| 19            | 14.028         | 3.083             |
| 20            | 15.351         | 3.228             |
| 21            | 15.766         | 3.347             |
| 23            | 17.384         | 3.717             |
| 25            | 18.587         | 3.978             |
| 27            | 21.182         | 4.281             |
| 29            | 21.549         | 4.523             |
| 30            | 22.224         | 4.706             |
| 32            | 23.549         | 5.037             |
| 35            | 27.202         | 5.444             |
| 37            | 29.063         | 5.764             |
| 40            | 29.277         | 6.087             |

Blender 3.5 Splash scheme

#### Table 6: <a href="#tab_bathroom_above_corner" id="tab_bathroom_above_corner"></a>

|               |                |                   |
| ------------- | -------------- | ----------------- |
| Vector length | Insertion time | Verification time |
| 2             | 2.313          | 0.657             |
| 5             | 5.012          | 1.152             |
| 7             | 10.228         | 1.498             |
| 10            | 15.495         | 1.997             |
| 12            | 17.667         | 2.415             |
| 15            | 19.627         | 2.964             |
| 17            | 23.986         | 3.311             |
| 19            | 26.091         | 3.738             |
| 20            | 27.808         | 3.816             |
| 21            | 28.326         | 4.080             |
| 23            | 31.014         | 4.479             |
| 25            | 32.523         | 4.770             |
| 27            | 34.605         | 5.151             |
| 29            | 36.062         | 5.462             |
| 30            | 36.456         | 5.710             |
| 32            | 38.921         | 6.031             |
| 35            | 42.441         | 6.496             |
| 37            | 44.138         | 6.919             |
| 40            | 49.456         | 7.458             |

Bathroom Above Corner scheme


---

# Agent Instructions: 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:

```
GET https://docs.inferix.io/inferix-whitepaper/appendix-d-performance-evaluation-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.