Re: [elephant-devel] Severely poor performance in some obvious cases

2007-11-29 Thread Alain Picard
"Henrik Hjelte" <[EMAIL PROTECTED]> writes: > We have recently discovered some performance (and possibly other) > problems, you might even call them bugs, with both map-index and the > current implementation of cursors in the postmodern backend. Alex > Mizrahi will reimplement things in a new way

Re: [elephant-devel] Re: Severely poor performance in some obvious cases

2007-11-29 Thread Alain Picard
"Alex Mizrahi" <[EMAIL PROTECTED]> writes: > AP> Am I missing something really basic here? > > actually it's quite strange situation that you have *many* employees > with same name but you want just one (random one). i cannot imagine > why one needs this in real world.. I didn't say they have th

Re: [elephant-devel] Re: Severely poor performance in some obvious cases

2007-11-29 Thread Robert L. Read
On Thu, 2007-11-29 at 21:25 +0200, Alex Mizrahi wrote: > > RLR> Postmodern does exactly the same thing that CL-SQL does in this > RLR> respect; the code was copied directly from the CL-SQL code. > > from original Henrik's announcement: > > > The implementation is actually quite different

[elephant-devel] Re: Severely poor performance in some obvious cases

2007-11-29 Thread Alex Mizrahi
??>> I'm surprised you are seeing this difference on Postmodern, unless ??>> your input name is matching a large number of objects (i.e. s is ??>> large). I had thought that the native PostgreSQL backend, ??>> postmodern, ??>> fixed the linear cost problem of CL-SQL indices and provides the

[elephant-devel] map-index

2007-11-29 Thread Alex Mizrahi
hello i'm now trying to improve implementation of cursor in postmodern backend. it would be nice to optimize it for usage patterns of map-index, but map-index implementation frightens me: is there a reason for such complexity? for example, just to enumarate index with two values it does calls l

Re: [elephant-devel] Severely poor performance in some obvious cases

2007-11-29 Thread Robert L. Read
On Wed, 2007-11-28 at 18:37 -0500, Ian Eslick wrote: > I'm surprised you are seeing this difference on Postmodern, unless > your input name is matching a large number of objects (i.e. s is > large). I had thought that the native PostgreSQL backend, > postmodern, > fixed the linear cost probl

Re: [elephant-devel] Severely poor performance in some obvious cases

2007-11-29 Thread Robert L. Read
I used CLSQL recording in the past when I have been debugging. I think that is the best way to do it; I wouldn't want to put such a think in Elephant, since it would be very backend-specific. On Wed, 2007-11-28 at 18:37 -0500, Ian Eslick wrote: > There is not SQL recording built into Elephant tha

Re: [elephant-devel] Re: Severely poor performance in some obvious cases

2007-11-29 Thread Robert L. Read
On Thu, 2007-11-29 at 16:16 +0200, Alex Mizrahi wrote: > AP> Am I missing something really basic here? > > actually it's quite strange situation that you have *many* employees with > same name but you want just one (random one). i cannot imagine why one needs > this in real world.. > > or you'

[elephant-devel] Re: Severely poor performance in some obvious cases

2007-11-29 Thread Alex Mizrahi
AP> Am I missing something really basic here? actually it's quite strange situation that you have *many* employees with same name but you want just one (random one). i cannot imagine why one needs this in real world.. or you're saying that all have different names, but it still does consing?

Re: [elephant-devel] Severely poor performance in some obvious cases

2007-11-29 Thread Henrik Hjelte
We have recently discovered some performance (and possibly other) problems, you might even call them bugs, with both map-index and the current implementation of cursors in the postmodern backend. Alex Mizrahi will reimplement things in a new way with the eye for performance, this work will probably