i’ve detected an issue with one of our huge jobs after having them migrated from DS 4.0 to DS 4.1.
In DS 4.0 the Job was running between 7 and 8 Hours.
In DS 4.1 the job is running between 10 and 12 hours.
So i started to analyze were this bad performance can come from…
The first huge dataflow takes 3:28 hours instead of 1:41 hours!
So it needs 50% more in this Dataflow only.
The submitted SQLs against SAP R/3 are the same (validated via “Displayed optimized SQL”) especially the WHERE clauses. So it’s not extracting / caching more data…
So i found out that in DS 4.0 the Monitor log file is around 66MB, in DS 4.1 it’s around 172MB!!
Could it be that this slows down the processing about 50% ?
Additionally to that it ignores the refresh period of 5 seconds.
If i set it to 120 seconds it’s also refreshing every second!!
We read via old RFC read table method some SAP table with join conditions against Oracle tables.
Why it ignores the refresh period?
Is there a possibility to disable the monitor on Job level?
setting it to zero definitely disables to monitor, but for all of my batch work I want to get the monitor result, just not populate some pointless log entry.
But where in the “add schedule” section i can change the monitor rate?
Haven’t found this there…
Additionally to that changing the monitor sampling rate for old RFC Table read method doesn’t affect anything.
It refresh every second…if i do 5 seconds, 120 seconds, or more…
So i want to completly deactivate it because it writes 172MB monitoring file (or more) and seems to cost 4 hours additional run time.
In DS 4.x the monitor sample rate is a value in seconds, not number of rows. The default is 5 seconds. If you want to change that you have to do it before you schedule the job in the Management Console or before using the Export Execution Command. It has to be set in the properties of the job itself.
How big is that Excel sheet? Anything complicated going on?
I certainly haven’t seen any such problems with 4.1 although most of our clients have now moved to 4.2 SP1/SP2 (largely due to the MS SQL 2012 and Windows Server 2012 support).
this is a bug, and happens only for Excel reader in both DS 4.1 and 4.2, instead of writing the rows every n sec (n is the value of monitor timer rate) the monitor log is written for every row causing performance issue