FTC TEAM ROCKERZZ – Great Progress & Important Technical Notes
First of all, good and hard work from the FTC Team Rockerzz.
Really proud — a small team with solid effort can achieve big things.
Keep going strong.
Reply #5 (technical) with a simple flow-mapping concept so everyone can easily understand the idea.(Anoth) No need design make it simple with effort less
---
Simple Concept Flow – Why SSR Must Not Run on the FTC Core
Problem (easy explanation):
If Server-Side Rendering (SSR) runs on the same CPU core that our FTC realtime service uses, the CPU gets overloaded.
This causes delays or missed events in FTC.
Basic Flow Diagram
[FTC Core] → Handles realtime operations → Must stay fast and free
If SSR runs here:
[FTC Core] → FTC + SSR share CPU → Delay → FTC performance drops
Better approach:
[FTC Core] → only FTC tasks
[Separate Core / Service] → SSR rendering (isolated and safe)
This ensures FTC latency stays stable and predictable.
---
Pre-Production Notes (Phase 1, 2, 4 Testing)
Good improvements so far.
Isolation tests, load tests, and multi-core scheduling tests show that you are moving in the right direction.
---
Post-Production / Large-Scale Notes
When scaling up to many users or large rendering loads, SSR must be fully isolated so it never interrupts realtime FTC processing.
---
Do (Recommended)
Isolate SSR on another core using CPU affinity or cgroups.
Offload rendering to a separate worker service (container, VM, or serverless API).
Use asynchronous queues and backpressure (RabbitMQ, Kafka, SQS) to manage render jobs.
Add rate limits, timeouts, and circuit breakers to rendering service calls.
Monitor CPU, latency, and queue depth, and trigger autoscaling before performance issues occur.
---
Don’t (Avoid)
Do not run CPU-intensive SSR on the same core that handles FTC or other realtime tasks.
Do not allow uncontrolled parallel renders that can saturate the CPU.
Do not rely only on manual restarts; use automated isolation and scaling.
---
Note to Admin:
This post is part of work documentation. You may remove it at any time without my permission.
