fP export time

[Kenneth Brody]

On 8/8/2014 11:57 AM, Don Coleman wrote:
> I have a long-time client who creates a monthly billing export.  Previously this export would take 2-3 minutes to create.  The user (Kerry) recently had her WINXP machine (export took 2-3 minutes to complete) replaced with a far more powerful WIN7 machine, but the export now takes 37 minutes to complete.  I also had their on-site I.T. person create the export from another user's machine (Pauline), and while on that machine it does take longer than the old WINXP machine, it is still faster than Kerry's new machine.  Does anyone have any thoughts on what could be causing this?  They use AVG Business Edition as their A/V, hosted on both the client and the server.  Disabling the AVG A/V on Kerry's new machine has no effect on the export time, 37 minutes (repeatable) with A/V enabled/disabled.  Their I.T. person sent me the basic hardware specs on each of the respective clients and server.
[...]
> Kerry's Old PC:
> ============
> - Windows XP SP3
> - 32-bit OS
> - Intel Pentium Dual CPU E2140 @ 1.60 GHZ
> - 1.0 GB RAM
>
> Export took 2-3 minutes, max (I'm told)
>
>
>
> Kerry's New PC:
> =============
> - Windows 7 Professional SP1
> - 64-bit OS
> - Intel Core i5 4570 @ 3.20 GHZ
> - 8.0 GB RAM
>
> Export started at 9:25 AM
> 9:35 record selection began (first record selected)
> 10:00 record reading/selection ended
> 10:02 generating output completed (37 minutes)

The export actually only took 2 minutes.  Reading the file took 25 minutes.

What happens in dclerk if the scan for a record, using a non-indexed field, 
for a value that doesn't exist?  How long does that take?

> Pauline's PC:
> ==========
> - Windows 7 Ultimate SP1
> - 32-bit OS
> - Pentium Dual-Core E5400 @ 2.70 GHZ
> - 4.0 GB RAM
>
> Export started at 7:41AM
> 7:46 record selection began (first record selected)
> 7:55 record reading/selection ended
> 7:57 generating output completed (16 minutes)

Again, it's the reading of the file, not the export itself, that's taking 
the time.

What about this system's time for scanning for a record that doesn't exist?

Also, what about the original "fast" system?

[...]

That said, I have seen cases where a NIC is "too fast" for the cable it's 
using, causing transmission errors and retries, which actually make it 
slower than using a slower transfer rate.  (ie: we have some older cables 
running behind the walls, where running at 100Mbps is slower than 10Mbps. 
Fortunately, we're mostly wireless now.)

What network speed are the systems running at?  Can you try running the new 
system at a slower rate?

-- 
Kenneth Brody