[Topaz-dev] Mulgara Performance Woes

[Life is hard, and then you die]

On Tue, Mar 04, 2008 at 11:47:23AM +1000, Andrae Muys wrote:
> 
> On 03/03/2008, at 9:47 PM, Life is hard, and then you die wrote:
> 
> > [warning: the rest here is _not_ applicable to our current mulgara
> > usage which is via soap, but to the future usage which is via RMI]
> >
> > On Sat, Mar 01, 2008 at 09:51:46PM +1000, Andrae Muys wrote:
> >>
> >> On 01/03/2008, at 3:45 AM, Russell Uman wrote:
> >>
> >>>
> >>>> We need some idea of A) how long transactions are being kept
> >>>> open,
> >>>
> >>> because certain things take a long time to serve (search, feeds,
> >>> etc.).
> >>> because once the pub-app times out its connection to mulgara,  
> >>> mulgara
> >>> keeps the transaction open for a long time, hopefully waiting.
> >>
> >> There's been a pending feature request to provide some sort of
> >> keepalive on session connections for quite a while now, maybe this is
> >> the impetus needed to push it to the front of the queue.
> >
> > Hmm, I thought RMI controlled connections? Is there a way to manage
> > them? Or are you talking about having mulgara issue some sort no-op on
> > the client side periodically in hopes of keeping the underlying
> > rmi/tcp connection open? Do you know, does Sun's RMI implementation
> > multiplex different requests over a single tcp connection, or does it
> > use a separate connection for each request in progress?
> 
> Not so much a question of keeping the connection open, as detecting  
> when the other-side goes away. I haven't taken the time to  
> investigate exactly what is happening on the wire - although 10- 
> minutes and a copy of ethereal will resolve that if we need to :).

I suppose this is where RMI's distributed-gc comes into play. Though I
wonder what exactly they do if one party becomes unreachable from a
network perspective.


  Cheers,

  Ronald