EmployeeFrom my past conversations with support, the only real difference was that it provides a dedicated execution space (JVM) for script execution with dedicated memory. So if you uses Agent your script/batchscript/etc run inside Agent memory space and have the possibility to exhaust Agent memory or terminate Agent if your scripts do not exit properly; with SSE you can only impact the SSE process itself. That being said, SSE didn't exist for many years and all scripts ran in Agent, so keeping it that way isn't a big deal really, especially if you don't do a lot of LogicModule dev. SSE only kicks on if there is an available memory of 50% of the RAM allocated to Agent anyway (meaning if you configure a collector that uses 8GB for Agent, it would want 4GB for SSE) and if that's not available it will suspend usage of SSE anyhow. Also, because of that memory allocation logic, you'll find the docs recommend not using SSE with many virtual-machine collectors due to how they report RAM to the underlying guest OS (see the docs). We have a hodge-podge of SSE and non-SSE collectors at various clients and there's been no discernible difference operationally. We have this community DS that's the subject of this thread running on a dozen non-SSE linux VM collectors and it's had no issues.
