Good day , advanced user settings can be enabled during compilation62e5dd8a-f984-4093-bc0a-ebaff2f39db0-image.png
Optimizing BAS for Massive Scaling on High-End Server (768GB RAM) - Need Technical Advice
-
Hello BAS Support Team,
I am writing to seek advanced technical advice regarding scaling a compiled BAS script to run hundreds of concurrent threads. I am automating browser tasks for a streaming platform (Kick.com).
My Hardware Setup:
CPU: AMD EPYC 9754 (128-Core Processor, 265-Thread)
RAM: 768 GB
Network: High-speed connection with Premium Proxies.
The Current Issue:
When I try to run 4 separate instances of my compiled script simultaneously (to maximize my hardware), I get massive failure rates with errors like "Timeout during loadPage".I previously contacted Telegram Group Comunity support, and they suggested the issue might be a Disk I/O speed limit and recommended creating a RAM Disk. I created a 300GB RAM Disk (Z:) using ImDisk, but I still have some technical questions to ensure I am doing this correctly.
Could you please clarify the following points for a high-end server setup?
-
RAM Disk vs. Profile Storage (Cookies):
Is it enough to just place and run the compiled BAS .exe files from the RAM Disk, or must the script also save the browser profiles (cookies, cache) strictly to the RAM Disk?
I prefer saving profiles on my local C: drive so I don't lose user login sessions when the server restarts. Will saving profiles on the C: drive cause the Disk I/O bottleneck to return, even if the .exe is on the RAM Disk? -
Premium Fingerprint API Limits:
I am using the official Premium Fingerprint module. If I run 4 separate instances of the compiled script at the exact same time each one only 100 thread so total 400 threads , using the same Fingerprint API key, will the server block my requests? Do I need 4 separate API keys for 4 instances, or should I stagger the startup times (e.g., wait 5 minutes between starting each instance)? -
Best Practices for Maximum Threads:
Given my massive hardware capabilities, what is the official recommended approach to achieve the maximum number of concurrent browsers on a single RDP?
Is it better to run one massive instance with 400 threads? and i tried this and not work got same problem "Timeout during loadPage" after open 100~120 thread .. or you have another way ?
Or is it better to run 4 separate instances with 100 threads each?
I want to fully utilize my server's resources without crashing the BAS browser engine. Any detailed documentation or advice on this massive scaling would be highly appreciated.
Thank you for your time and excellent software.
Best regards,
-
-
Hello,
This may not directly address your questions, but contributing to the community is important, so I'd like to offer a different suggestion.
I've heard that even changing the user-agent on the KICK side is sufficient; some even do it with a request. (I find it interesting, but if they're really doing it, it's not impossible.)
There's an excellent node.js running within BAS. If high security isn't required, try doing it with node.js - playwright, which is faster and uses less memory and very fast fast fast browser.