From: thhal at mailblocks.com (Thomas Hallgren)
Date: Wed, 18 May 2005 23:40:07 +0200
Subject: [Pljava-dev] What about using the server jvm ?
In-Reply-To: <20050518212945.75919.qmail@web60320.mail.yahoo.com>
References: <20050518212945.75919.qmail@web60320.mail.yahoo.com>
	<428BB637.6040402@mailblocks.com>
	<thhal-0uk5nAxmzzTYD5CS4t8O7dqxayIg5Zk@mailblocks.com>
Message-ID: <thhal-0uk5nAxuzzTYNhVmqWWWw21HmxhCnKy@mailblocks.com>

Juan Manuel Diaz Lara wrote:

> I made a very small test, I chaged my path to jre/bin/server in place 
> of jre/bin/client,  and executed SELECT 
> sqlj.get_classpath('public')... it worked.
>  
> I would like comments about the implications: what about performa ? 
> and compatibility ?

PL/Java supports both the client and server JVM. The best choice depends 
on your use-case. The server will typically outperform the client during 
long and heavy sessions at the cost of higher memory consumption and 
some degraded performance initially. Since a PostgreSQL backend is 
single-threaded and each session spawns a JVM of it's own, the higher 
memory consumption imposed by the server may not be worth it.

Regards,
Thomas Hallgren