We do need to sort results by the custom weight properties, they are sort
of customized versions of the swishranking that are specific to the
"quality" of the records as they pertain to various user groups who search
Can i get away without presorting even though i want to sort by them
any other thoughts on how to reduce the extended cpu time. it seems to
sit on one custom weight in particular, in this case for probably 11 out
of the 13.5 hours.
866 476 7862 x902
On Sat, 21 Oct 2006, Bill Moseley wrote:
> On Sat, Oct 21, 2006 at 11:53:51AM -0700, brad miele wrote:
>> any ideas on how i might make it a little faster? the delay is always at
>> sorting a numeric cusomweight property.
> Do you need to sort results (or limit with -L) by that property? If
> not tell swish not to pre-sort it, and any other properites you don't
> Elapsed time: 13:36:49 CPU time: 13:31:48
> That's a lot of cpu time.
> Bill Moseley
> Unsubscribe from or help with the swish-e list:
> Help with Swish-e:
Received on Sat Oct 21 13:39:28 2006