Periodic reboots of Epicor 10.2.400?

Thanks so much, you are always a ton of help!!!

If you were in my shoes and ownership’s answer was, nope we’re not paying for an upgrade… Is there anything you would do given we seem to have a memory leak(eg recycle app pool ever couple weeks, or recycle app pool when RAM get above x%, etc)?

There is an IIS Setting you can turn one which automatically recycles Apps if they get too big… Its a terrible Idea… but it could work I hate myself for even suggesting it… Do some research on it, but that would cause the app to self cycle when it gets unruly

@josecgomez would this explain our high RAM utilization given low number of users?

We had Live, Pilot, Test, and Train app servers running as well as EWA for each(8 total Epicor application pools, plus 2 for quickship, and RDWebAccess - not sure what this is). We pretty much never use Pilot, Test, or Train so support suggested turning them off and seeing what difference we see in RAM utilization and only turn them on when they are needed(turned off 6 application pools). We went from 13GB of RAM for IIS to a little under 7GB. That’s a lot of RAM for app servers no one was even using :slight_smile:

I’d also would turn off Live-EWA as I think it’s the browser based access. We don’t use it, but since I’m not sure left it on as to not guess and break anything.

We’ll what you showed me on the screenshot. At 13GB thats a single app server (maybe live?)

So I don’t think so keep an eye on it and see if it spikes back up

For future me or anyone reading this wondering which application pool is using all the RAM, I found in task manager if you add Command Line column you can see which Epicor application pool corresponds to which process. In my case I started them all back up and it looks like our Epicor application pools cost us about 2GB of RAM each after initial startup…

3 Likes