On Mon, Apr 24, 2017 at 8:30 PM, Wayne Stewart via 4D_Tech < 4d_tech@lists.4d.com> wrote:
> Mine performs similarly slowly (5-6 records per second) but it sends only > one record per web service call. > > A smarter and less lazy person than me would bunch a few records into the > one call, use compression etc. One day I might implement this but you > never can tell, I think beer is more interesting. > As you're pointing out, your code is not optimized yet you're getting twice as many records. Something seems amiss. The payload is sent in a single web service call with data from multiple records being packed into the BLOB sequentially. It's complex code, elegantly written. Some payloads are pretty good sized but I don't recall if compression is used. The transmission time is very reasonable - everything just goes in the crapper when it comes to unbundling. I haven't timed the decoding vs encoding and then vs actually writing to disk. That might provide some insight. -- Douglas von Roeder 949-336-2902 ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
