From: Mike S. <ms...@md...> - 2008-02-20 17:55:06
|
Is this remote synchronization, or just local? If just local, when you say you turn it off, are you turning off OSC pooling and only using a single OSC? Or are you literally just turning off the syncing? ms On Feb 20, 2008, at 12:35 PM, Kieran Kelleher wrote: > I was importing and validating 4 million or so records using editing > context batching and recycling (and the importing thread has its own > OSC too BTW) > > With OSC sync *off* in the app, the memory stays very low (150MB) and > no problems encountered. > > With OSC sync *on* the memory just keeps growing and growing until I > run out of memory at 1.5GB. > > I thought maybe the OSC synchronizer was creating snapshots in the > main OSC when receiving notifications of inserted EO's in the import > thread's OSC, but looking at the synchonizer source (which I am not > fully understanding ... yet), it appears that > ERXObjectsStoreCoordinatorSynchronizer > .InsertSnapshotProcessor.processGI > D does not do anything.... this is puzzling. > > Any ideas why this would be the case? > > Regards, Kieran > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |