Support Board
Date/Time: Mon, 25 May 2026 18:21:08 +0000
Post From: FAST DOM can it even be done in Sierra Chart?
| [2026-05-25 13:12:46] |
| TopGunTrader - Posts: 309 |
|
Honestly, Sierra should offer a separated low-latency trading/UI architecture for power users. The core problem is that fast order handling, DOM rendering, ACSIL studies, chart drawings, GDI overlays, and custom tools are too entangled. For users like you, Sierra should provide a mode where orders and cancels are never waiting behind chart drawing work. What Sierra should build: Dedicated Order Thread Order submit/cancel/modify should run on a protected high-priority path, separate from chart redraws and study calculations. Dedicated DOM Rendering Thread The Trade DOM should not be blocked by chart studies, GDI overlays, or sc.UseTool drawing load. Separate ACSIL Drawing Budget Let studies draw, but cap or schedule them so they cannot starve order/DOM updates. Order State Priority Lane Working order add/remove/move visuals should update before non-critical drawings. If an order is canceled, the DOM should reflect “cancel requested” immediately, even before final confirmation. Native Fast Drawing API Sierra should expose a modern retained-mode drawing layer, not force heavy UseTool updates or awkward GDI overlays for dense tools. Per-Study Performance Telemetry Show exactly which study is consuming update time: calculation milliseconds drawing milliseconds number of drawings adjusted GDI callback time skipped frames order-overlay delay Study Isolation One slow/heavy study should not make the entire chart/DOM feel sticky. At minimum, Sierra should allow studies to run on worker threads when they are read-only/data-prep only. DOM-First Mode A setting like: “Prioritize order entry and Trade DOM updates over all custom drawing/study rendering.” That mode should guarantee this order: 1. receive order/depth update 2. process cancel/modify/submit 3. update order state visuals 4. update DOM price/depth visuals 5. run lower-priority chart drawings/studies The blunt version: Sierra is incredibly powerful, but it still behaves like a single highly-loaded workstation app. People doing dense ACSIL/GDI/order-management work need something closer to a trading terminal engine with strict priority lanes. If Sierra gave us order thread isolation + DOM render isolation + study performance telemetry, your current project probably would not need to exist. |