user2960: 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:

(For example, see http://bitcoinity.org/markets, and http://bitcoin.clarkmoody.com/ )
How is the "engine lag" time calculated?

user3292: From the Mt. Gox API Documentation:

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


user3675: 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.

2960: <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.stack.imgur.com/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>
 3292: <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>
 3675: <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>
