Understanding the Trace Log (Configurator)

Epicor ERP 10
1

Hi everyone, a lovely sunny afternoon and I am here trying to figure out why our configurators are taking so long to load, the more lines on a quote or order the longer they take. Over a hundred lines and we are talking minutes. I have attached an excerpt from the trace log which has very high numbers compared to anywhere else. Does anyone know what is happening here and why the numbers would be so high?
This was run using a quote with 30 lines already on it. I started the trace, pressed the Configure button, waited approx 40 seconds for the configurator to load then stopped the trace.

image
image1025×264 11.4 KB

If anyone can help it would be much appreciated. This performance is killing us at the moment.

2

Are the lines all using the same configurator? Or is it also when the other lines are non-config parts?

And does your configurator have lots of lookup or BAQ driven fields?

Other things that might help shed some light on it:

  • Does it still happen if you close the order entry form and reopen it? (Guessing it could be a memory leak)
  • Does re-configuring an existing line bring it up faster?
  • Any difference if it’s the 1st line vs the last?
3

Hi Calvin,
All the lines are using a configurator. Everything we sell is configured using one of around twenty configurators.

Closing and reopening the page makes no difference.
Re-configuring brings the configurator screen up at what I think is normal speed (interestingly enough)
Re-configuring shows no difference in load time between the first and last line.

The configurators contain between 1 and 4 BAQ driven fields, between 4 and 12 UD methods and a maximum of 20 lookups. Once loaded, they run perfectly well. It’s just the load time. I don’t actually know what is happening in that time.