Any advice, how to manage a lot of steam-user client?

[charon]

The steam-user instance use tcp or websocket to keep alive to the steam server, it's stateful,

not like steamcommunity connection, the http connection is stateless, so we can cache the http cookies, and load cookies as we needed any time, no need to keep a steamcommunity instance.

but the steam-user use a alive connection, so we have to always keep a steam-user instance in memory, when there are a lot of steam-user instances, it's hard to manage them, how many steam-user instance show be managed in one node.js process and how to partition a lot of steam-users, it may be a large project.

any advice or experience about this ? thank you.

[Dr. McKay]

There's no real limit on how many steam-user instances you can run in one process; your biggest limitations are going to be memory and IP addresses.

[charon]

10 minutes ago, Dr. McKay said:

There's no real limit on how many steam-user instances you can run in one process; your biggest limitations are going to be memory and IP addresses.

if all the instance are managed in one process, every time reboot the process all steam-user need to login again, it' a big affect!

[Dr. McKay]

Yes, for that reason you probably want to split up your stuff into multiple processes.