Re: EOF related objects present a lot in the heap
Re: EOF related objects present a lot in the heap
- Subject: Re: EOF related objects present a lot in the heap
- From: Musall Maik <email@hidden>
- Date: Mon, 29 Apr 2013 11:11:36 +0200
Am 26.04.2013 um 21:21 schrieb Chuck Hill <email@hidden>:
>
> On 2013-04-26, at 12:12 PM, Ramsey Gurley wrote:
>> Disadvantages of persistent sessions:
>>
>> * Hard. Everything must be serializable on your session. Your EOs, your WOComponents, everything. Fixing serialization errors is no walk in the park.
>> * Serialization adds a few milliseconds wait to the RR loop.
>> * Database load. Every RR loop is two selects and an update on a session row. Even if you isolate the session in their own database, there's a wall there. Get large enough and you'll hit it. Postgres 9.2 can handle about 14,000 writes per second according to what I've read.
>
> memcached, or something like that, might be an interesting alternative.
What would be the point of freeing some memory in WO only to allocate the same memory in another process?
Maik
_______________________________________________
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