D
dbeavon
Guest
I didn't see any way in the PASOE configuration to put a cap on the memory utilization of a multi-session agent process. Am I missing something? In our case, I think the problem is related to a certain analysis-report that is pulling tons of data into memory-resident Temp-Tables. (It isn't a "leak" as such.) I suspect it is related to the fact that the user was too greedy in their time period selection (probably pulling all data for a month or year). Since we have so many reports that are moving into PASOE, it is hard to micro-manage the memory utilization of each. I'm not 100% sure of the reason for the memory consumption. But on a general basis, I think it would be better if the "ms-agent" could enforce a memory restriction. Any of our reports that needed more memory would die, rather than cause the entire server to become unstable. Hope this is clear. We are migrating our reports from an HP-UX server that had almost 400 GB of physical RAM! And the "classic" appservers could take as much as they wanted.
Continue reading...
Continue reading...