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: Chuck Hill <email@hidden>
- Date: Mon, 29 Apr 2013 15:35:18 -0700
On 2013-04-29, at 2:11 AM, Musall Maik wrote:
>
> 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?
I was considering how to make persistent sessions faster, not save memory.
--
Chuck Hill
Executive Managing Partner, VP Development and Technical Services
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/gvc/practical_webobjects
Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C!
Global Village Consulting ranks 76th in 24th annual PROFIT 200 ranking of Canada’s Fastest-Growing Companies by PROFIT Magazine!
_______________________________________________
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