Suggestions for "latency-based" throughput issue?

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Boaz Bezborodko
> Sent: Thursday, February 20, 2014 10:37 AM
> To: Filepro-List at Lists. Celestial. Com
> Subject: Suggestions for "latency-based" throughput issue?
> 
> I'm running Windows Filepro off files served on a Linux server using
Samba.  I
> find that there seems to be a hard limit on my throughput of about 4MB/s
per
> operation.  That is, each instance of Filepro is limited
> to 4MB/s.   I see this on many operations that simply update files and
> also on index rebuilds.  If I run, say, three Filepro windows, each
rebuilding it's
> own file index, each is still running at 4MB/s, my computer sees a total
> throughput of about 12MB/s.  I've seen this limitation even when I
replaced
> the server with a somewhat faster server and it was the same when I had
> fewer disks (and lower local throughput) on the older server.  I figure
that the
> limitation is not the server or the PCs, but the latency between the two
when
> doing the database operations.
> 
> I know that switching to Filepro on Linux would make everything faster,
but
> I'm not ready to go that route yet and in most cases this is not a
> problem.   In the meantime there are occasional large jobs that I would
> like to speed up, if possible.  Does anyone have any suggestions on how to
> program it so that large jobs are automatically broken up and started in
> separate windows?
> 
> --

Where does your configuration point to PFTEMP, is this on a local machine or
the server?

What anti-virus software are your using?  Have you configured it not to scan
fp and filepro directories (folders)?

Is your configuration using a mapped drive or UNC?  The mapped drive will be
faster the UNC.

How fast are your local drives?

Depending on the size of your indexes, you may need to tune them using some
of the filepro index configuration variables.

Try
 set pfbixnodesize=10
set pfbixbuild=2

and then test your rebuild time.


Richard Kreiss
GCC Consulting

Office: 410-653-2813