It would appear that the back-fill and charting features, which are bandwidth-intensive, share the same communications pipeline as our quotes and trade activities. That means that our trades, fill notifications, and quotes are competing with the back-fill and charting requests to get through in a timely fashion.
If this is the case, I must say that I am extremely disappointed. The back-fill and charting features are bandwidth hogs for which latency is not a consideration. That traffic should ideally be sent out through another pipe entirely. At the very least the routers should be set to place that traffic at the lowest priority using the Quality of Service features that are now standard in all commercial routers and gateways. This would ensure that back-fill/charting *never* cause any performance or service degradation for quotes, orders, and fill notifications.
-Raystonn
If this is the case, I must say that I am extremely disappointed. The back-fill and charting features are bandwidth hogs for which latency is not a consideration. That traffic should ideally be sent out through another pipe entirely. At the very least the routers should be set to place that traffic at the lowest priority using the Quality of Service features that are now standard in all commercial routers and gateways. This would ensure that back-fill/charting *never* cause any performance or service degradation for quotes, orders, and fill notifications.
-Raystonn