fP export time
Bruce Easton
bruce at stn.com
Wed Aug 13 12:19:05 PDT 2014
Don:
Just curious - considering this from your reply to Ken: "We also ran the
export again, this time adding the beginning & ending date on the
extended selection screen, which normally has two search criteria values",
are these fields that are normally used on the extended selection screen
associated fields (where what is being tested not a real field but the
associated field id)?
In any event, have you tried rebuillding all the indexes built on fields
that are used on the extended selection screen to see if there is any
difference?
Bruce
On 8/13/14 12:58 PM, Don Coleman wrote:
> Ken:
>
> We were able to perform the test you requested this AM, on the primary client used to run this export. The other client we tested the export time on was unavailable this AM. Scanning for a non-existent value (but meeting its assigned edit) on a non-indexed field scanned the entire file in 2:20 (two minutes twenty seconds, 610376 records). We also ran the export again, this time adding the beginning & ending date on the extended selection screen, which normally has two search criteria values. Normally, the client does not enter the date on the extended selection screen, but enters it via select processing. The date selection is the only thing occurring in the select processing. I did note I am not using lookup- to speed up the select processing, but can certainly add it.
>
> Anyways, today's export time with the beginning & ending dates added to the extended selection was 27 minutes, better than last weeks 37 minutes, but still extraordinarily long. On her previous very low-powered work station, this export took 2-3 minutes.
>
> Don Coleman
> Donald G. Coleman, Consultant
> 402 Andrew Circle
> Indiana, PA 15701
> (724) 349-6302
> (412) 849-2589 (cell)
>
> ---------- Original Message ----------------------------------
> From: Kenneth Brody <kenbrody at spamcop.net>
> Date: Fri, 08 Aug 2014 16:03:48 -0400
>
>> On 8/8/2014 3:31 PM, Don Coleman wrote:
>>> Bruce:
>>>
>>> The exact menu command line is:
>>> \fp\rreport dmexcept -f Point_Click_Care -v askdate -s -u
>>>
>>> Point Click Care is the A/R application I export the data to.
>>> In the fP Configuration Editor I have PFIXS=ON, so no -j menu flag necessary.
>> [...]
>>
>> Since your previous post with the timings showed that the slowness was the
>> sort/select phase, it could be the "askdate" sort/select processing.
>> However, since you say it runs faster on the older systems, it's not likely
>> to be related to processing.
>>
>> I haven't seen an answer for my previous question about using dclerk to
>> search a non-indexed field for a value that doesn't exist, and comparing
>> timings across workstations.
>>
>> --
>> Kenneth Brody
>>
>
>
>
>
>
> ________________________________________________________________
> Sent via the WebMail system at mail.dgcreact.com
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
More information about the Filepro-list
mailing list