Suggestions for "latency-based" throughput issue?

[Boaz Bezborodko]

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?

-- 

Mirrotek International, LLC
90 Dayton Avenue
Building 1-F
Passaic, NJ  07055

Tel:  973-472-1400 x.112
Fax:  973-472-5170


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com