public inbox for [email protected]  
help / color / mirror / Atom feed
Subject: [Pljava-dev] Is it safe to use multi-threaded PL/Java in single-threaded postgres process?
Date: Mon, 14 Apr 2014 20:54:51 +0900
Message-ID: <D40AEDF3497A484BBCC1DEB79CD5CB3E@maumau> (raw)
In-Reply-To: <[email protected]>
References: <30A6B4B499494CED93770BBC4835840C@maumau>
	<A832684586A84610AD7173AB42138F38@maumau>
	<5F50DAFCABA4426FA54E9D8D0B78B38B@maumau>
	<[email protected]>
	<1F2A8D3FBCC3447391A3520631ACBD25@maumau>
	<[email protected]>

From: "Thomas Hallgren" <thomas at tada.se>
> 3. For a test like yours, the time it takes to execute the actual 
> statement is important. The execution may be so slow that the overhead 
> imposed by the network call becomes negligible. A test using a lightweight 
> "SELECT 1" instead of the heavier "UPDATE testtable" would reveal such 
> issues.

Yeah, I thought this is the most likely.  We are trying to speed up batch 
jobs dramatically, and I hoped PL/Java's in-process architecture would 
contribute to that.

But I wonder why in-process execution didn't make a big difference.  I 
expected several times of difference because I saw the PollPosition 
benchmark results at http://hsqldb.org/.  It compares HSQLDB's in-process 
and client-server execution models.  I assume the client and the server ran 
on the same host.

Anyway, in-process and out-of-process execution doesn't seem to make a big 
difference for batch jobs which issue many SQL statements.

Regards
MauMau





view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Subject: Re: [Pljava-dev] Is it safe to use multi-threaded PL/Java in single-threaded postgres process?
  In-Reply-To: <D40AEDF3497A484BBCC1DEB79CD5CB3E@maumau>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox