Jiwa

we have a file watcher csv import ( file per order ) that has taken about 2 minutes each per file ( generally about 160 lines per order ). This was done on the test sever at customer site with limited resources.
However the database is large 100 gigs with the so_lines having about 28 million lines.

======
• I have installed the database , and tested the same scenario on a laptop ( with SQL server on a spin disk similar to the DEV server )
The speed of the file process seemed to be half of the dev server ( 1 minute vs 2 ).

I have also looked at any other areas that could be delaying and have found nothing. After discussions with the internal team , the assumption is the 1 minute speed with a 166 line order was expected.

During debug i found that :
Out of the entire operation ( of the 1 minute ) , about 25 seconds was to add the lines to the sales order and about 35 seconds was used by the Jiwa engine to save. on the SalesOrder.Save() method.


I would like your thoughts on this .

Take a look at these

https://docs.jiwa.com.au/display/J7UG/Changing+the+SQL+version+of+my+database

https://docs.jiwa.com.au/display/J7UG/Slow+performance+when+retrieving+data

And if it is the customer I think it is, then try running the archiving process on the sales orders as it has a lot data going back well over 10 years.

Which version of Jiwa is this happening in?

I believe that changes regarding sales order and quote imports were made in 7.2.1 that may speed things up.

I am pretty sure its already 7.2.1 as this is for a November Go Live

7.2.1

I suspect doing what I suggested above will make some difference as I don't think the database has ever seen a maintenance plan.