There is a flag in the Product entity that can beused to prevent the creation of product keywords; unfortunately the flag is ignored by the eca associated to the features of the product (imo this is something we should fix).
Kind regards, Jacopo On Jan 14, 2012, at 1:59 AM, Adrian Crum wrote: > I tried to find out why a data import for a bespoke (made-to-order) > manufacturer was taking WAY too long. Turns out it was keyword indexing EECAs. > > Each product has dozens of product features, and it also has a manufacturer > ID. The indexProductKeywords is called for the product, each product feature, > and the ID. As a result, one product takes several seconds to store. > > Then the BOM for each product needs to be imported. The > indexWorkEffortKeywords service is called for each work effort in the BOM. > Why do I want my BOM work efforts keyword indexed? > > This is insane. Why would anyone set up EECAs like that? > > I would like to turn those EECA services into jobs that run on a regular > basis, so real work can get done in real time. > > What do you think? > > -Adrian >
