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:13:02 +0200
re-post as I forgot to post to the list
Am 26.04.2013 um 21:12 schrieb Ramsey Gurley <email@hidden>:
> Advantages of persistent sessions:
>
> * Frees memory at the end of the RR loop
> * Easier to manage deployments. Sessions are distributed across instances.
> * Sessions can last as long as you want.
>
> 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.
Do you think it would be possible to not serialize out the session on each RR loop, but instead having a short timeout delay (like 10 or 30 seconds), make the session persistent once the timeout is reached, and keeping the actively used sessions in memory?
Could that be "best of both worlds"? :-) Of course you wouldn't spare the serialization debugging.
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