David:

The transmission time is very manageable — these folks send in data from
very remote locations and the payload always arrives at the server. The
BLOB's are sent via web services and, IIRC, the BLOB's are pretty good
sized, some being over 100k.

The deal breaker is that the code is only updating about 3 records per
second it can sometimes takes days for the server to catch up.

--
Douglas von Roeder
949-336-2902

On Mon, Apr 24, 2017 at 7:42 PM, David Adams via 4D_Tech <
[email protected]> wrote:

> > The current approach has got to be quite inefficient. The problem I've
> got
> > is that I can't come up with anything other than a WAG as to how much
> > faster it will be.
>
> It's been some time since I tested out size v. speed relationships in a
> similar setup. And, of course, it depends  on your hardware, network, etc.
> But, when I last tested it, the size of the download correlated pretty
> exactly with the download time. I mean end-to-end. So, the overhead on
> compression paid for itself nearly instantly. (The overhead proved to be
> small.) 30% smaller payload, 30% less time required to download it.
>
> Like you, I wasn't clear what the breakeven point was for the expense of
> compression. I couldn't find a place where compression was a bad bet.
>
> Assuming I'm on track with what you guys are talking about and
> haven't wandered off into the woods again...
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to