looong saveChanges in a background task
looong saveChanges in a background task
- Subject: looong saveChanges in a background task
- From: OC <email@hidden>
- Date: Mon, 23 Feb 2015 19:43:27 +0100
Hello there,
this time, my problem -- at least I hope so -- is going to be simple and straightforward.
My application allows users to import CSV; since it is a lengthy task and sice we need it to stay responsive for others, the import runs in a background task (an ERXLongResponseTask) with a lowered thread priority.
Nevertheless, there still is a problem: if there's a number of imported objects, the threadEC.saveChanges() at the end can take a small eternity. And, given EOF is single-thread, it blocks other threads' access to the DB. Which, alas, rather kills the responsiveness for other users.
One solution would be to use more EOF stacks, but I am told setting ERXObjectStoreCoordinatorPool.maxCoordinators>1 leaks memory as a sieve if one uses BLOBs, and we use them pretty often.
Another solution would be saving changes after importing each 100-odd items, but that brings problems with potential fail of some later save and a need to clean up the previous ones.
Is there another solution to the problem which I have missed? Or do I have to cope with the partial-import-saving?
Thanks a lot,
OC
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden