Replies: 2 comments 3 replies
|
Good news: your topology is right, you're just missing one step — upgrade Compute to Tier 2 immediately. The math: sustained load on this level is ~8 req/s (5 base + 15-burst every 5s), but Compute Tier 1 only processes ~5 req/s. The queue doesn't add throughput — it only smooths the bursts. With that 3 req/s deficit, a 200-slot queue saturates at ~72 seconds, which is exactly what you experienced. After buying the Queue ($45) you have $135 left — the Tier 2 upgrade costs $100, so you can afford it right at the start. Hover the Compute node and click the green upgrade arrow. Tier 2 handles ~13 req/s, which beats the 8 req/s load, and the queue never saturates. That said — you're right that the game doesn't teach this anywhere. The level text says the queue "prevents drops," which implies it's sufficient on its own. It isn't (queues never add capacity, in this game or in real infrastructure). I'll update the level briefing to make that explicit. Thanks for the report! |
|
Thank you for the reply and making this amazing game for people to learn cloud infrastructure. What I did is place a Queue and route the traffic NLB -> Queue -> Computer (T2). $35 left and start the game. At t=9s, I have $47 and the Queue had 21/50 request processing. So I add another Queue immediately and unlink the old queue until both queue are balanced. At t=22, I have only $32 and each Queue's load already build up to 36/50 and 40/50. At t=25 right after the 5th wave of burst request. Queue 2 nearly saturated 49/50. and immediately unlink it and put a new Queue on time. At t=30, Queue 1 nearly saturated 47/50, so I also unlink it leaves Queue 3 to absorb the burst. After that I link both Queue 1 and 2 back to the network prepare for the 7th wave. At t=35, right before the wave, the load of Queue 1,2,3 are 42,37,39 respectively. after the wave, become 46,41,47 but I have only $29 which insufficient for me to purchase a new Queue. At t=38, I manually balance the load, and they are all 45 requests now and still unable to build a new Queue ($37). At t=42, All Queue saturated after wave 8 and dropped 5 requests. still unable to purchase a new Queue $41 At t=44 I finally have enough budget for a new Queue and route all traffic to the new Queue (4). The queue 4 immediately saturated after wave 9 and 10. and I link Queue 1-3 back to network (load: 40~43) Right before 1m5s's wave. All queue saturated and 33 requests dropped, but I got $51 so I build a new Queue immediately and route all traffic to it. successfully with stand the 1m5s and 1m10s, but all Queue's load are 48-50 1m15s, the new wave arrived but all of the Queue are saturated, lost all the requests. but still have 75% of reputation. and I make a new Queue and route all traffic to it. After a new wave, I link all Queue back to network and still dropping requests. right now the total dropped requests increase to 54. With the same logic, I fail the campaign right after 1m52s. I'm still wonder should I unlink those old Queue after placing a new Queue and balance them manaually. Look forward to your reply. |
|
Forgot to mention, using demolish tool only 50% refund instead of 100% refund. Is it because of campaign mode? |
|
Your play-by-play just helped find a real engine bug — thank you for writing it down minute by minute. You did everything right. The problem was on our side: the Queue→Compute path was silently capped at ~4 req/s no matter how upgraded your Compute was. Compute pulled at most one request per frame from the queue, and each request spends ~half a second in flight — so even your T2 (which can process ~13 req/s) was being starved by the pipe feeding it. That's why adding more queues didn't help: you were adding buffers in front of a choked pipe. Fixed in #172 and already live. Your exact topology (ALB → Queue → Compute T2) now passes the level — in testing, queue depth peaks at ~17 out of 200 over the full 90 seconds instead of saturating. On the refund: 50% on demolish is intentional (it prevents free rebuilding on every traffic shift), not campaign-specific. There's an open discussion about tuning it in #129. Give the level another run — would love to hear if it feels right now. |
Uh oh!
There was an error while loading. Please reload this page.
Level 5 cannot be done. I place queue before computer and the queue got saturated before I have enough money to upgrade the computer. After the queue was saturated, reputation keep dropping and loss the game.
I couldn't find any useful tips inside the manual. is my setup has problem or 5 secs burst is too short?
Thank you so much!
All reactions