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

[Ian Eslick]

Alain's solution to the get-instance-by-value is the correct one.   
It's an API issue, not a fundamental one.

That is to say if you know you want only one of a potentially  
duplicate set from a slot index, get-instance-by-value should just use  
get-value on that index.  I implemented that function a long time ago  
and didn't really think through it, it was just syntactic sugar for  
(car (get-instances-by-value)) which I ended up using alot.

The map-index and cursor issues I will talk about in a follow-up e-mail.

Ian

On Nov 29, 2007, at 6:25 PM, Alain Picard wrote:

> "Alex Mizrahi" <killerstorm at newmail.ru> 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 the same name, at least I don't think I did.
> I have millions of employees, each with a unique name, and
> want to pull one back with an indexed, efficient search.
>
>> or you're saying that all have different names, but it still does
>> consing?
>
> Yes - that is what I am saying.
>
>              cheers,
>                        --ap
>
>
> -- 
> Please read about why Top Posting
> is evil at: http://en.wikipedia.org/wiki/Top-posting
> and http://www.dickalba.demon.co.uk/usenet/guide/faq_topp.html
>
> Please read about why HTML in email is evil at: http://www.birdhouse.org/etc/evilmail.html
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel