Re: Interesting Benchmarks -- SQL, RPG, Journaling, and Triggers

Charles Wilt wrote:

The RPG update process read the file in arrival seq, and updated. %fields
was _not_ used as the READ and UPDATE was done directly to a data
structure. Thus, %fields would have no effect and probably isn't even
valid.

The SQL update process did an "update myfile set myfield = myField + 1"

Wow. I'd have expected the SQL update process to WAY outperform the RPG in this case. Updating 2.9 million records without having to "pass through the MI layer" - that is, the SQL engine should have done all the work without coming back to the HLL program - as opposed to the 2.9 million round trips for the RPG program should have resulted in a clear win for SQL. Maybe the clock time savings reflected it, but even so I'd have expected a lot more benefit for SQL.

Maybe they've increased the performance of RPG I/O as well, and aren't telling us <grin>.

Joe