> For the complete documentation index, see [llms.txt](https://docs.inferix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inferix.io/inferix-whitepaper/economic-model/inferix-bench-and-ibme/ibme.md).

# IBME

Short for *Inferix Bench Minutes Efficiency*, is an index used to evaluate the working efficiency of a set of nodes $$\mathcal{N}$$ over a working period $$P$$, determined by the formula of the total IBM paid over the total apparent IBM:

$$
\text{IBME}*{P}\left(\mathcal{N}\right) \triangleq \frac{\sum*{n \in \mathcal{N}} \text{IBM}*P \left(n\right)}{\sum*{n \in \mathcal{N}} \text{IBM}\_P^a \left(n\right)}
$$

where $$\text{IBM}\_P \left(n\right)$$ is the customer paid IBM for node $$n$$ and $$\text{IBM}\_P^a \left(n\right)$$ is the apparent IBM of node $$n$$ calculated by multiplying the IB of a node by the elapsed time (in minutes) of period $$P$$. We observe that IBME is always a figure below 100% and the higher the IBME ratio, the more efficiently the network operates.

#### Figure 15: <a href="#figure_15" id="figure_15"></a>

<figure><img src="/files/6N7WAxLaZq0IMey7KQx6" alt="" width="375"><figcaption><p>IBME flywheel</p></figcaption></figure>

Recent reports from DePIN projects have highlighted a significant issue: while the number of nodes participating in the network is very high, many of these nodes are either inactive or active but not receiving any service requests. Inferix solve this problem by controlling the IBME.

In addition to planning and adjusting the [Emission Plan](/inferix-whitepaper/economic-model/burn-mint-work-token-issuance-model.md), IBME also assists Inferix Governance in making decisions related to the use of the Inferix Foundation's funds for promotional activities aimed at increasing supply or attracting service demands.


---

# 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.inferix.io/inferix-whitepaper/economic-model/inferix-bench-and-ibme/ibme.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.
