IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  dtxpage Utility generates different outputs for the same input

    Posted 02/14/09 03:36 AM

    Originally posted by: harishtd


    Dear Experts,

    I am running dtxpage on my map to find out the optimal page size/ page count settings for the work files.
    Although my input file and my map source remains unchanged the utility gives me different suggestions of page size and page count for every run.

    Am i missing something here?

    Version Info
    8.1.0.4(22) on WinXP

    Run 1
    Optimal page settings for Map_Frontend_to_Backend.mmc are SIZE: 16 COUNT: 20
    Run 2
    Optimal page settings for Map_Frontend_to_Backend.mmc are SIZE: 256 COUNT: 16
    Run 3
    Optimal page settings for Map_Frontend_to_Backend.mmc are SIZE: 64 COUNT: 12
    Run 4
    Optimal page settings for Map_Frontend_to_Backend.mmc are SIZE: 64 COUNT: 12

    Thanks in Advance
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 2.  Re: dtxpage Utility generates different outputs for the same input

    Posted 02/16/09 02:39 PM

    Originally posted by: SystemAdmin


    Performance Tuning is not an exact science. What else is running on your system? They will affect outcomes.

    I wrote my own performance tuning script and I can select the number of iterations as well as file vs memory. I would enter 100s of runs if practical. The results data was then read into a spreadsheet and the data sorted to determine what settings resulted in the best performance. Most of the time the default settings were the best.

    Jim Divoky
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 3.  Re: dtxpage Utility generates different outputs for the same input

    Posted 02/17/09 09:07 AM

    Originally posted by: phil2030


    It is ages since I bothered playing with page sizes. I think you will find it will vary based on what your machine is doing along with the complexity of your type tree and the data your parsing at any given run. Personally unless your running into problems or performance is mind-numbingly bad (in which case you might look at your type tree also) I would leave as the default.
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange