Diagnosing Slow Async Cryptocurrency Data Updates

Summary

The document compares an asynchronous script that requests market data for many cryptocurrency pairs in a local VS Code run with its behavior in a live environment. The local log shows updates arriving about a second apart, while the live log shows selected updates roughly seven seconds apart. The code creates concurrent data-fetching tasks for a list of high-volume pairs, gathers them, and then pauses before repeating the cycle.

It raises the possibility that the live environment, rather than the coroutine approach itself, accounts for the slower updates. However, it provides no investigation or confirmed explanation. It does not report request timing, API rate limits, deployment resources, or whether data processing blocks the event loop, so the source of the delay remains unresolved. The examples illustrate a performance discrepancy, not a tested diagnosis or a trading signal.

Key ideas

• The script gathers concurrent data requests for a list of cryptocurrency pairs.
• The local and live logs show different intervals between updates.
• The document asks whether the live environment causes slower updates but does not establish why.
• API limits, network latency, and blocking work are not examined.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.