Sage X3 slows to a snail pace every day for no apparent reason

Hi all

We are relatively new on the Sage platform and we are experiencing a problem where our X3 access just slows down to a snails pace every day for no apparent reason. We have upgraded RAM and CPU to this virtual machine, and when it slows down we sometimes find that the CPU has gone to 99 or 100%. On most occassions the CPU & RAM are around the 30-40% mark yet the X3 app just hangs. Our Sage partner technical team has spent weeks tracing this and can find no fault. We are on Version 7.

This is drastically affecting productivity and we are bforced to reboot the server around once per week in order to be able to work again. Sometimes we run a batch file that stops all the pertinent services and restarts them and this has helped to a small degree.

  • 0
    Hi Angus,

    - What process in windows is taking up the CPU usage?
    - How many CPU cores are allocated to this machine?
    - Are all cores CPU bound (sounds like yes when it is 99 or 100% used)?
    - Does the slow down happen at the same time every day?
    - Do you have any batch processes set to automatically run at the a specific time, and does this cross with the time you are noticing the slow downs?
    - Are you running imports in X3? Is this contributing to the CPU usage?
    - Do you have any Node.exe processes that are taking more than 1GB of RAM? If so, go to Admnistration > Servers > Hosts and bump up the "Number of Web service child processes"
    - Is your Sage platform all on one machine? If so, where is the CPU utilization coming from? Is it SQL Server, the Application server for X3, the Syracuse Server, the Print Server, a Java Server perhaps, or where exactly?

    Hope this helps,
    Bob
  • 0
    Angus,

    We are dealing with our own performance issues but can't peg the issue to a particular time of day, during a call with our support provider and a Sage agent, she mentioned that running batch processes like FUNWIPACC every 15 to 20 minutes can improve performance as longer intervals require more more lines per journal entry (we were blowing through the 5000 line cap regularly). Don't know if this helps but I thought Id mention it.