From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Volkan YAZICI Newsgroups: gmane.lisp.guile.user Subject: Re: Guile Interpreter as a Standalone Server Date: Sat, 21 Oct 2006 00:26:50 +0300 Message-ID: <20061020212650.GE2076@alamut> References: <20061005180035.GA1376@alamut> <87fydizpg9.fsf@ossau.uklinux.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1161384423 18180 80.91.229.2 (20 Oct 2006 22:47:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 20 Oct 2006 22:47:03 +0000 (UTC) Cc: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sat Oct 21 00:47:02 2006 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gb38g-0001od-Pj for guile-user@m.gmane.org; Sat, 21 Oct 2006 00:46:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gb38g-0002ez-B4 for guile-user@m.gmane.org; Fri, 20 Oct 2006 18:46:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gb1v5-0000Qf-OU for guile-user@gnu.org; Fri, 20 Oct 2006 17:28:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gb1v3-0000H3-1e for guile-user@gnu.org; Fri, 20 Oct 2006 17:28:46 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gb1v2-0000G4-IU for guile-user@gnu.org; Fri, 20 Oct 2006 17:28:44 -0400 Original-Received: from [212.175.13.129] (helo=fep01.ttnet.net.tr) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gb1v2-0005r6-AA for guile-user@gnu.org; Fri, 20 Oct 2006 17:28:44 -0400 Original-Received: from (unknown) by AVGW-I-1.ttnet.net.tr with smtp id 7e11_f66ecf3e_6081_11db_84cf_001422175f0e; Sat, 21 Oct 2006 00:28:43 +0300 Original-Received: from alamut ([85.99.4.1]) by fep01.ttnet.net.tr with ESMTP id <20061020212842.NWP27706.fep01.ttnet.net.tr@alamut>; Sat, 21 Oct 2006 00:28:42 +0300 Original-Received: from (dsl.dynamic859941.ttnet.net.tr [85.99.4.1]) by AVGW-I-2.ttnet.net.tr with smtp id 2b4a_ee588dd0_6081_11db_9b6d_001422175ed8; Sat, 21 Oct 2006 00:28:41 +0300 Original-To: Neil Jerram Content-Disposition: inline In-Reply-To: <87fydizpg9.fsf@ossau.uklinux.net> User-Agent: Mutt/1.4.2.1i X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:5619 Archived-At: Hi, On Oct 20 09:45, Neil Jerram wrote: > Volkan YAZICI writes: > > - Parse & execute faster. (We won't need to create a new process > > everytime.) > > Is this for a specific application, out of interest? Yes, it's for PL/scheme. [http://plscheme.projects.postgresql.org/] > > - Cache parse plans. > > I don't understand what this item means. You know, there're some procedure volatility levels in SQL. For instance, non-volatile (mmiutable) procedures always return same result as long as you supply same argument values. (Yes, we've caching for this in PL/scheme.) For volatile procedures, result depends on lots of outsource data, therefore its result is undeterminable. But, I had thought that at least I can make PL/scheme perform better by just executing the previously cached parse plan (by skipping parsing from scracth phase) parameters) of a volatile procedure called with exactly the same arguments. Regards. _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user