Re: Local connection in web app

["John Patterson" <dev_johnpatterson@xxxxxxxxxxx>]

Hi

Thanks for your response.  I would just like to get some clarification on
running an embedded database.  One of the main reasons I would like to do
this is my virtual Linux server has only 64 MB RAM.  I do not want the
memory overhead of another VM if I can avoid it.

Have others found that the server runs faster in a seperate VM?  This seems
strange.  What could cause this?

How likely is it that McKoi will crash the VM.  Has this happened to anyone
here?

Thanks,

John

----- Original Message ----- 
From: "John Zoetebier" <john.zoetebier@transparent.co.nz>
To: <mckoidb@mckoi.com>
Sent: Wednesday, December 17, 2003 10:35 AM
Subject: Re: Local connection in web app


> On Wed, 17 Dec 2003 10:18:54 -0000, John Patterson
> <dev_johnpatterson@hotmail.com> wrote:
>
> > Hi,
> >
> > I was wondering if it is possible to use a 'local' JDBC Connection in a
> > multithreaded environment (ie web app).  I would like to do this to save
> > on the network layer overhead.
>
> You can run McKoi in embedded and server mode.
> In embedded mode the database runs in the same VM as the client.
> My experiences though are that McKoi runs faster in server mode.
> An other thing you have to be aware of is that running the database in a
> separate JVM has a distinct
> advantage as a crashing database server cannot bring down your client
> application.
> You can monitor your database server and restart it without the client
> noticing.
> The network layer is just one of the many considerations you have to make
> to optimize the architecture.
>
> -- 
> John Zoetebier
> Web site: http://www.transparent.co.nz
>
>
> ---------------------------------------------------------------
> Mckoi SQL Database mailing list  http://www.mckoi.com/database/
> To unsubscribe, send a message to mckoidb-unsubscribe@mckoi.com
>
>