On the i, it uses the same underlying code as FNDSTRPDM. Depending on what's in the filter you're searching, it may have to do it multiple times, and of course each instance is dependent on how fast or slow your i is at searching your source. I don't do a lot of searches because we have huge numbers of source members on a slow, overloaded partition (we get 0.6 processors and 3 GB of memory for a LOT of developers...). Most of what I need to find I can get to faster via Hawkeye.

Dave Shaw
Mohawk Industries


----- Original Message ----- From: "Justin Taylor" <JUSTIN@xxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, August 31, 2009 1:56 PM
Subject: Re: [WDSCI-L] WDSCI-L Digest, Vol 7, Issue 245


You're right, it does work (albeit badly) in WDSc. I searched a single filter and it took 37 minutes (yes MINUTES) to complete. I did the same search via CTL-H, and it finished in less than a minute. Three guesses which one I'll be using in the future


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.