Re: EOF / multithreading app design question
Re: EOF / multithreading app design question
- Subject: Re: EOF / multithreading app design question
- From: Ken Anderson <email@hidden>
- Date: Tue, 1 Dec 2009 23:28:06 -0500
We're already processing hundreds of messages per second, leveraging
thousands of EOs... so not really.
On Dec 1, 2009, at 9:48 PM, Andrew Lindesay wrote:
Hi Ken;
I do this sort of thing; feeding in workload via messaging queues
and process it.
If you had a number of instances consuming from the queue rather
than focussing on threading within one instance, I wonder if you
really need to do anything special around EOF concurrency within a
single JVM? In my applications, the batch processing occurs on a
different EOObjectStoreCoordinator to the regular user-processing
and so there is no contention between the two. This seems to work
well for me.
...a single context for all this stuff takes up a few hundred
megabytes already.
Can you not break down the workload (presumably by message) and
create a new EC each time you have to do some work?
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
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