Does Replikanto send signals in a queue or in parallel?

This article explains how Replikanto dispatches trade signals to follower accounts and network nodes, and which factors affect how fast that copying happens.

Queue or threads?

Replikanto uses a parallel approach to send trades to remote nodes. It does not place trade signals in a queue and send them one after another — it uses multiple threads so that trades are copied to multiple followers simultaneously.

Why CPU cores matter

Because the copying work is spread across threads, the hardware running Replikanto has a direct effect on throughput:

• A higher number of CPU cores increases the effectiveness of the parallel trade-copying process.
• The speed of the CPU also affects the overall time it takes to copy trades.

Other factors that affect copy time

• Number of follower accounts — the more followers there are, the longer copying may take, even with parallel processing.
• NinjaTrader processing — NinjaTrader handles the order submissions, and the efficiency of that step impacts the overall copy time.
• Network — local network connections are typically faster than internet connections. Remote copying depends on server locations, which can add latency.
• Broker processing — once the order is submitted to the follower account, everything the broker does before the market fill is outside the copier's scope, but it still adds time to the trade's lifecycle.

What latency to expect

The latency depends on how the trades are being copied:

• Local accounts (same machine) — copying between accounts on the same NinjaTrader instance is typically between 10 ms and 200 ms, measured from the moment an order submitted on the leader account is notified, to the moment Replikanto submits the order on the local follower account.
• Local Network Mode (LAN/WiFi) — copying between two Replikanto instances on the same local network typically ranges between 50 ms and 500 ms.
• Remote Copy over the internet — sending trade signals to remote network nodes over the internet is typically between 100 ms and 1000 ms.

See What is Replikanto's trade copy latency in milliseconds? for the full breakdown.

Keep your version current

Replikanto is constantly updated to improve its parallel processing and minimize delays. Running the latest version of the product is recommended for optimal performance.