Michael Crozier <crozierm at conducivetech.com> writes:

>> >> I guess that in my case the improvement was more like 95%.
>> >
>> > I also saw a significant increase. ?The difference between my "fast"
>> > machine and "slow" machine seemed to indicate that the difference was
>> > primarily CPU related.
>>
>> That's consistent with it using a seq scan and having to sort the table.
>
> It was performing indexed lookups for both versions of the query.  EXPLAIN 
> showed that the only difference was the tableid filter(s). It sounds odd, but 
> I'm fairly confident thats what I was seeing.  Unfortunately I didn't keep 
> notes and can't be completely certain.
>
> The index and static group size were definitely the big improvment, though.

I think I missaid part of that.

It still needs to do a sort in order to put things in order of the
"action sequence".  That will be an in-memory (in the PG backend)
sort.

>> Oh, dear.
>>
>> Fortunately, you can deactivate that at runtime by setting the time
>> it's trying to aim at to 0.
>
> I misread the documentation, thanks for setting me straight.

If you can poke at why it seemed unclear, I'd be happy to improve the
docs in the hope of others not falling into the same trap.

If you think some things should be documented better, or that
something's confusing, by all means let me know.  I may occasionally
suffer from "writer's arrogance," but improving the docs can help
prevent people from needing to ask "dumb questions" here, so I'd
rather see them improve :-).
-- 
let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];;
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)