When developing locally with a database of 588 agents, less than 10 of which were active, I noticed that each node process immediately used 2GB of memory on startup. I tried removing the agent.initialize calls (which populates the conversation objects, bringing them into memory) and switching to using a single Agenda job definition rather than one per agent, but neither change made a difference. Further investigation may be warranted....
When developing locally with a database of 588 agents, less than 10 of which were active, I noticed that each node process immediately used 2GB of memory on startup. I tried removing the agent.initialize calls (which populates the conversation objects, bringing them into memory) and switching to using a single Agenda job definition rather than one per agent, but neither change made a difference. Further investigation may be warranted....