On Tue, Apr 25, 2017 at 6:36 AM, James Crate via 4D_Tech < [email protected]> wrote:
> If you can easily modify the code, you could try commenting the SAVE > RECORD command(s), and replace any queries for an existing record with > REDUCE SELECTION($tablePtr->;0). That should be quick and easy and will > show the speed of the unpacking only. Alternatively, you could test > importing into an empty database, which should remove the impact of queries > and index updates. > > If there are many method calls and much pointer dereferencing, 4D will be > very slow interpreted but much faster compiled. > Jim: Excellent suggestions. Thank you. There are many, repetitive method calls. For example, each time the code converts a byte range to a longint, it calls a function that returns the byte order. As much as I never met a subroutine I didn't like, perhaps the sheer number of them is impacting performance. The idea of run a synch session and committing records is a winner. I'll give it a try. -- Douglas von Roeder 949-336-2902 <(949)%20336-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:[email protected] **********************************************************************
