Nikolai Haddad

The machine, then the proxies, then you. RAM goes first because every profile is a real browser process, so the concurrent count matters far more than the total — 500 profiles is fine, 50 open at once is a different question. Proxies go second, usually as cost rather than failure. But the constraint that actually caps people is process: naming, grouping and knowing which profile is which. That one does not scale by buying hardware.

Expected, in my experience. The first launch after a new engine build has caches to rebuild that every later launch reuses, so the first profile pays for the rest. If it is still slow on the third or fourth, that is different and usually points at the proxy handshake rather than the engine. I now update in the evening and let the first launch happen while I am not waiting on it.

Can confirm, seeing the same thing on my machine.

The built-in check tests the connection, not the session, so they can disagree.