> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/image-optimization-and-webp/image-optimization-analytics.md).

# Image Optimization Analytics

The **Analytics** dashboard provides visibility into how Medianova’s image optimization engine performs across your CDN resources.\
It highlights key performance metrics—such as **GPU utilization**, **processing throughput**, and **optimization efficiency**—to help you ensure consistent, fast, and cost-effective image delivery.

<figure><img src="/files/wudvQ06zTWmaoGWQuDVQ" alt="" width="563"><figcaption><p>Medianova Image Optimization Analytics</p></figcaption></figure>

#### Available Metrics

The **GPU Usage** chart visualizes how system resources are utilized during image processing and WebP conversion.

<table><thead><tr><th width="191">Metric</th><th>Description</th></tr></thead><tbody><tr><td><strong>Peak Usage</strong></td><td>The highest GPU utilization percentage observed during the selected time period.</td></tr><tr><td><strong>Average Usage</strong></td><td>The mean GPU workload over the reporting window.</td></tr><tr><td><strong>Time-Based Trends</strong></td><td>Shows fluctuations in GPU activity correlated with request load or time of day.</td></tr></tbody></table>

{% hint style="info" %}
Use shorter time ranges (e.g., last 1 hour) to analyze real-time optimization performance, or longer ranges (e.g., 24h/7d) for trend analysis.
{% endhint %}

#### How to Interpret Data

**1. High GPU Usage**

* Indicates heavy image transformation or large-scale WebP conversion.
* Expected during peak traffic or mass optimization operations.
* Sustained high usage may suggest scaling additional GPU resources.

**2. Low GPU Usage**

* Suggests reduced processing demand or effective caching.
* Typically means the system is efficiently serving pre-optimized images.
* If traffic is high but GPU usage remains low, caching and delivery optimizations are working as intended.

**3. Sudden Spikes**

* Can occur due to unoptimized workflows or irregular API request patterns.
* Investigate spikes to ensure consistent response times and workload distribution.

#### Optimization Opportunities

Regular monitoring of **GPU Analytics** helps identify areas where optimization can further improve performance:

* **Balance Workloads** – Distribute image processing evenly across nodes to prevent bottlenecks.
* **Improve Caching Efficiency** – Minimize repetitive optimization tasks for identical images.
* **Scale Resources** – Allocate or deallocate GPU nodes dynamically based on load.
* **Refine Parameters** – Adjust image resizing, compression, or WebP settings for cost-performance balance.

{% hint style="info" %}
Performance data can also inform future infrastructure planning, ensuring you scale only when necessary.
{% endhint %}

#### Why Analytics Matters

Monitoring **GPU Usage** ensures that Medianova’s Image Optimization system operates at peak performance, delivering measurable business benefits:

* **Faster Image Delivery** – Reduce latency through balanced edge processing.
* **Cost Efficiency** – Avoid over-provisioning GPU resources.
* **Reliability and Stability** – Prevent system slowdowns during peak image workloads.
* **Data-Driven Decisions** – Optimize configuration based on real metrics, not assumptions.

Efficient resource utilization directly contributes to smoother operations, improved user experience, and lower operational costs.


---

# 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://clients.medianova.com/products/performance-cdn/image-optimization-and-webp/image-optimization-analytics.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.