feat: add time and requirement doc

Signed-off-by: Barış Zeren <[email protected]>

README.md

@@ -248,11 +248,15 @@ bbox_validation:
   ```bash
   export PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True
   ```
+
+  You can also check the [Time and Requirement Analysis](docs/time_and_requirent_analysis.md) document to see the VRAM requirements for each model.
 </details>
 <details>
   <summary><b>Error 2: Tool is taking too much time to process</b></summary>
 
   The tool might take a significant amount of time to process images, due to the computational complexity of combining multiple models (GroundingDINO, OpenCLIP, YOLO, SegmentAnything).
+
+  You can check the [Time and Requirement Analysis](docs/time_and_requirent_analysis.md) document to see the time requirements for each model.
 </details>
 
 ### Citation

docs/time_and_requirent_analysis.md

@@ -0,0 +1,29 @@
+## Time and Requirement Analysis
+
+This document explains the time and requirement analysis of the unified model.
+
+📝 An RTX 3090 GPU was used for the time calculations
+
+### Time Analysis
+
+Since we are using couple of foundation model to anonymize images, the tool might take significant amount of time.
+
+You can see which model takes how much time per image in the following table:
+
+| Model Name         | Time per Image (ms)          |
+| ------------------ | ---------------------------- |
+| Grounding DINO     | `~300 ms`                    |
+| Segment Anything 2 | `~130 ms`                    |
+| Open CLIP          | `~30 ms` x `number of boxes` |
+| YOLO v11 X         | `~20 ms `                    |
+
+### Requirement Analysis
+
+You can see how much VRAM is required for each model in the following table:
+
+| Model Name         | VRAM Requirement (MiB) |
+| ------------------ | ---------------------- |
+| Grounding DINO     | `~1200 MiB`            |
+| Segment Anything 2 | `~448 MiB`             |
+| Open CLIP          | `~930 MiB`             |
+| YOLO v11 X         | `~864 MiB`             |