On Apr 25, 2017, at 12:01 PM,Douglas von Roeder wrote: > 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.
Here’s an idea. I’m assuming all the record processing is done in a single process. How much work would it be to modify the code so that it spawns multiple processes that can run at the same time? I don’t know the code, but maybe you could pass that big BLOG off to a method in another process and let it do the work. Have 3-4 of these processes all working at the same time. I wonder if that would give you performance boost. Have you checked to code to see if there is any throttling going on? Maybe there are some DELAY PROCESS commands sprinkled around to keep the sync process from saturating the server. Did you say it was running as a stored procedure, or is it running on 4D Client. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [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] **********************************************************************
