On Wed, Jul 2, 2014 at 3:49 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
Note that the thread you're linking to talks specifically about moving
away from SQL2XLS to SQL2JXL, due to performance issues with the
I think that such performance problems are quite common with utilities
which dynamically format the results of SQL queries into some other
format... particularly when Java is involved.
I don't think the "particularly when Java is involved" is a fair
assessment. Both SQL2XLS and SQL2JXL "involve Java". Yet SQL2JXL is
noticeably faster. The main thing that makes some POI-based solutions
slow is the RPG-to-Java interface. The more you have to call Java
from RPG, the bigger the overhead. Native Java is... well, not as
fast as pure C or pure RPG, but not as slow as Java-through-RPG.
And then of course there can be better and worse algorithms even
within one implementation language that can affect performance.
Have you considered streaming SQL result sets to .CSV instead?
Usually, CSV is one of the earlier ideas people come up with. Folks
turn to Excel mainly when CSV's shortcomings become deal-breakers.
But yes, if CSV is adequate, then it's a much faster-performing