flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Changes to BlazeDS addressing memory consumption
Date Sun, 26 Jul 2015 15:32:26 GMT
This is totally outside my area of expertise but just so I’m clear, are
you proposing weak references or hard references on a per-message basis,
or that the queue uses weak or strong for all of its messages?

If the former, that makes sense to me.  If the latter, I would be
concerned that it would introduce a more random behavior, and there is no
way to have one message be “required” when others aren’t required.


On 7/26/15, 8:22 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>I am currently digging into some of the problems reported to BlazeDSs
>memory consumption. While there seems to be a real problem in the cleanup
>of clients, there is one other problem that could eventually help systems
>with a high throughput of messages.
>Usually messages for a client are added to that clients message queue.
>Now sometimes there are messages that need to be delivered, but (at least
>im my usecases) most messages should be delivered, but if the server is
>under extreme load it wouldn't be that bad to have them dropped.
>One possible solution possibly resolving some of the memory problems
>would be to change the queues to use weak references, that the VM can
>clean them up if memory is low. I would like to extend the Message
>interface with an method that controls if weak or strong references
>should be used. I was thinking of setting a default on the channel and
>allowing to explicitly override this default in the individual message.
>What do you think? Would this option be ok for you?

View raw message