[rucksack-devel] rucksack performance

[Cyrus Harmon]

I guess performance is the only issue I can think of. Yes, you have  
to pay the cost of indexing either way, but, at least in many  
systems, it can be faster to do a bunch of "inserts" and then index  
the table, using rdbms-speak. It's not so much an issue of debugging  
performance problems, as working around the performance bottleneck of  
inserting into an index. I guess in an ideal world we wouldn't need  
to disable indexing during a bulk creation phase.

On Jan 12, 2007, at 3:32 AM, Arthur Lemmens wrote:

> Cyrus Harmon wrote:
>
>> Since the index code seems to be the bottleneck here, it would be
>> good to spend some time optimizing the index code as well. Also, some
>> API support for disabling indexing might be nice.
>
> It's not clear to me what disabling indexing would buy (assuming you
> want to re-enable it later on).  Maybe it helps to debug performance
> problems, but I don't think that's enough reason to add API support.
>
> Or are there other reasons to disable/re-enable indexing?
>
> Arthur
>