[JDEV] xdb

[Tim Ferguson]

I did some testing with this and I had some problems where it appeared to be
overrunning the buffers, can't say for sure as I was not given the time to
track down the problem.  It simply locked up my jabberd process and that is
my best guess.  This was when there was a heavy load where I had four
processes using the jabber test suite to create 4000 simultaneous
connections.  Somewhere around 700 connections I would get the lock up.
Sorry I can't be more specific, but even if it hadn't locked up I saw a huge
latency in logins when I had a separate xdb process so Ben is absolutely
correct in that it is very inefficient.

Tim Ferguson


-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of Ben
Schumacher
Sent: Monday, January 14, 2002 10:38 AM
To: jdev at jabber.org
Cc: jdev at codc.com
Subject: Re: [JDEV] xdb

On 9 Jan 2002, Petal wrote:
> Hi, can I run the xdb as a seperate process to the rest of the jabber
> server?
>
> ie, like you can run the transports as seperate processes..

It appears that in all the discussions of "The Important Things", your
message got lost in the shuffle. Yes. It is possible to run an
"xdb" component in an external Jabber process, although I wouldn't
necessarily recommend it. To do this, simply use <accept> in your <xdb>
configuration and set it up as you would any other external component.

The reason I would discourage this is that it is fairly inefficient as all
data going to the <xdb> component would need to be serialized into xml,
sent across the socket and then unserialized on the other end... which is
quite a bit of overhead compared to just passing around the data in
memory.

Is their a specific reason you're trying to externalize an xdb component?

Ben

_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev