anvil.server.RuntimeUnavailableError: Downlink disconnected when confronted with 130 simultaneous requests

[ianb]

I made this cloneable app a while ago to show off background tasks and timers, you might modify its use to stress test your system / persistent server calls:

What is the best practice for asynchronously loading component data?

Ok, so since I read what @rsmahmud did yesterday I was thinking how I would do the same thing, using just: components timer components background tasks Today I made a short example of async like behavior that does what @rsmahmud wants, but uses background tasks instead: [async_with_timers] It can still be optimized further, especially if used with other techniques to chunk the server calls into blocks that only cover what the user might want to see on one page (like a lazy loading type beha…

IIRC it had no problem launching 150 blocking background tasks, even without a persistent server.