> > We have checked situation when Assign process is compared to the not > closed > > periods (we have checked Internal shipment with 140 lines), with closed > > period (180k move lines "closed" and 33k "open") it was made in roughly > > 83seconds and without closed period it was made in 87 seconds (when all > > 213k moves were "open"). So 4,5% improvement... > > > > Which is not so much :) > > Normal you have optimized one call made by Move.assign_try. > > > However we have quite a numbers of moves, roughly around 250 k > > I don't understand for me you should have 180k + 33k = 210k.
around 40k are move lines in Cancelled / Draft / Assigned states. > > While not redoing the Assignation process, what would be ideas to speed up > > the process? Which part of Server should be altered? > > The drawback is that the Move.assign_try is doing a lot of single > write/copy. The write could probably be optimized to be combined but > hardly the copy. Also the call to assign could be done at the end with all the moves. > Finaly, the search of child location inside the loop could be > externalized with a cache. > > thank you for suggestions! -- Mindaugas Kasalynas
