You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by as...@googlecode.com on 2015/08/10 10:03:20 UTC
Issue 925 in asterixdb: Bloomfilter search preceded by primary index
lookup after secondary index search is nothing but overhead since all primary
keys returned from secondary indexes are all valid and exist.
Status: Accepted
Owner: kiss...@gmail.com
Labels: Type-Enhancement Priority-Medium
New issue 925 by kiss...@gmail.com: Bloomfilter search preceded by primary
index lookup after secondary index search is nothing but overhead since all
primary keys returned from secondary indexes are all valid and exist.
https://code.google.com/p/asterixdb/issues/detail?id=925
Bloomfilter search preceded by primary index lookup after secondary index
search is nothing but overhead since all primary keys returned from
secondary indexes are all valid and exist.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 925 in asterixdb: Bloomfilter search preceded by primary
index lookup after secondary index search is nothing but overhead since all
primary keys returned from secondary indexes are all valid and exist.
Posted by as...@googlecode.com.
Comment #2 on issue 925 by kiss...@gmail.com: Bloomfilter search preceded
by primary index lookup after secondary index search is nothing but
overhead since all primary keys returned from secondary indexes are all
valid and exist.
https://code.google.com/p/asterixdb/issues/detail?id=925
That's correct. I missed that.
But still the possibility to see the deleted secondary key from the
secondary index in reality could be very low.
We need to profile the pros and cons of using bloomfilter in this situation.
Probably, pin/unpin will be the major cost if the page is not in the
buffercache already plus the overhead of going through buffer cache's
critical section. Other than that, computing hash value will be the next
major cost.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 925 in asterixdb: Bloomfilter search preceded by primary
index lookup after secondary index search is nothing but overhead since all
primary keys returned from secondary indexes are all valid and exist.
Posted by as...@googlecode.com.
Comment #1 on issue 925 by kiss...@gmail.com: Bloomfilter search preceded
by primary index lookup after secondary index search is nothing but
overhead since all primary keys returned from secondary indexes are all
valid and exist.
https://code.google.com/p/asterixdb/issues/detail?id=925
I just captured Yingyi's question here:
------------
In theory, a returned primary key could be deleted because secondary index
search does not lock anything...
Is the overhead mostly from pin/un-pin BF pages?
------------
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Re: Issue 925 in asterixdb: Bloomfilter search preceded by primary
index lookup after secondary index search is nothing but overhead since all
primary keys returned from secondary indexes are all valid and exist.
Posted by Yingyi Bu <bu...@gmail.com>.
In theory, a returned primary key could be deleted because secondary index
search does not lock anything...
Is the overhead mostly from pin/un-pin BF pages?
Best,
Yingyi
On Mon, Aug 10, 2015 at 1:03 AM, <as...@googlecode.com> wrote:
> Status: Accepted
> Owner: kiss...@gmail.com
> Labels: Type-Enhancement Priority-Medium
>
> New issue 925 by kiss...@gmail.com: Bloomfilter search preceded by
> primary index lookup after secondary index search is nothing but overhead
> since all primary keys returned from secondary indexes are all valid and
> exist.
> https://code.google.com/p/asterixdb/issues/detail?id=925
>
> Bloomfilter search preceded by primary index lookup after secondary index
> search is nothing but overhead since all primary keys returned from
> secondary indexes are all valid and exist.
>
> --
> You received this message because this project is configured to send all
> issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>