Yeah, I gave some thought to this a while back (but didn't actually do
it) ... The issue is that EOF's problem is not that it's CPU or memory
bound, its problem is that it is a single-lock basically non-
concurrent architecture. Distributing it with Terracotta just causes
MORE lock contention on a single EOF stack. The only way to scale
with EOF is by having multiple stacks, whether that is in a single
instance or across multiple instances, and Terracotta doesn't really
have much to offer you at that point, so I never went any further with
it. Using it for the appserver layer is potentially interestesting,
but it's hard to get classloader separation within WO to be able to
set it up properly.
ms
On Apr 3, 2008, at 8:37 AM, Travis Britt wrote:
(Sorry if this comes through twice, first version seems to have been
eaten.)
Has anyone done any investigation into using Terracotta with EOF?
I didn't find anything but wanted to make sure before I dig in.
tb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
