<p>From the <a href="https://en.bitcoin.it/wiki/MtGox/API/HTTP/v1#Order_lag">Mt. Gox API Documentation</a>:</p>

<blockquote>
  <p><strong>Order lag</strong><br>
  <code><a href="https://data.mtgox.com/api/1/generic/order/lag">https://data.mtgox.com/api/1/generic/order/lag</a></code><br>
  The "lag" value is the age in microseconds of the oldest order pending execution. If it's too large, it means the engine is busy, and the depth is probably not reliable</p>
</blockquote>

CC BY-SA 3.0
2013-03-29T00:42:39.920Z
2013-03-29T00:42:39.920Z
nivs
<p>It is the difference between current timestamp and the submission timestamp of the oldest order submitted, which has not yet been processed by the order book.</p>

CC BY-SA 3.0
2013-03-28T23:00:20.283Z
2013-03-28T23:00:20.283Z
Bob
<p>When looking at external API-driven charts of Mt Gox trades, there is a "Trading engine lag" shown, which shows the backlog of orders queued and waiting-to-be-executed, relative to the present time:</p>

<p><img src="https://i.sstatic.net/lVPFN.png" alt="enter image description here"></p>

<p>(For example, see <a href="http://bitcoinity.org/markets" rel="nofollow noreferrer">http://bitcoinity.org/markets</a>, and <a href="http://bitcoin.clarkmoody.com/" rel="nofollow noreferrer">http://bitcoin.clarkmoody.com/</a> )</p>

<p>How is the "engine lag" time calculated?</p>

<trading><mtgox>
How is "engine lag" on Mt Gox calculated?
gosmond
# How is "engine lag" on Mt Gox calculated?

(Asked by: username_0 on 2013-03-28)

When looking at external API-driven charts of Mt Gox trades, there is a "Trading engine lag" shown, which shows the backlog of orders queued and waiting-to-be-executed, relative to the present time:

![enter image description here](https://i.sstatic.net/lVPFN.png)

(For example, see <http://bitcoinity.org/markets>, and <http://bitcoin.clarkmoody.com/> )

How is the "engine lag" time calculated?

**Tags:** trading, mtgox


---

## 2 answers

### Answer by username_2 on 2013-03-28. Score: 6 | Accepted answer

It is the difference between current timestamp and the submission timestamp of the oldest order submitted, which has not yet been processed by the order book.


---

### Answer by username_1 on 2013-03-29. Score: 5

From the [Mt. Gox API Documentation](https://en.bitcoin.it/wiki/MtGox/API/HTTP/v1#Order_lag):

> **Order lag**  
> `https://data.mtgox.com/api/1/generic/order/lag`  
> The "lag" value is the age in microseconds of the oldest order pending execution. If it's too large, it means the engine is busy, and the depth is probably not reliable


---

