Re: Interpreted vs. Compiled - current comparison

2016-10-19 Thread Chuck Miller
For me compiling is not longer about speed at all but it sis about control. When you compile you control when and how updates are made. In source structures, it iOS too easy to make a change wit h bad results. Compiling solves that as you can create release schedules which include testing. Addi

RE: Interpreted vs. Compiled - current comparison

2016-10-18 Thread Dennis, Neil
> Are there any recent comparative performance tests available? Every database will perform differently based on how it is written. Some commands are compiled directly to machine code in these they may execute up to 100x faster, others require calls to the 4D engine. Some will have no improveme

Re: Interpreted vs. Compiled - current comparison

2016-10-18 Thread Kirk Brooks
David, I'll amplify what Jeff said by including text manipulation including web areas. As a rule of thumb I'd say anything your databases do that takes long enough to put up a progress indicator (except printing and some searches) will be faster by a factor of 3 - 20+. On Tue, Oct 18, 2016 at 9:5

Re: Interpreted vs. Compiled - current comparison

2016-10-18 Thread Jeffrey Kain
Depends on your application. Is it all data entry and record manipulation? If so, hardly any benefit will be seen from compiling. If it's code intensive, array intensive, object intensive, etc. then you'll see a big improvement. I'd say the differences between interpreted and compiled code rem