Re[2]: Some DataStage questions
Posted: Mon Apr 02, 2001 9:24 am
Thanks, Ray!
But this is very strange. The length of constraints is about 1K. The condition is simle, it check the equality of string in DB and inut string and works wrong (debuger shows identical values, Ardent considers conversly).
I dontt think that in our case (Sun Enterprise 3500, 2Gb Ram,
IDS.2000) performance is determined by external factors. The simple row update in the 50000 records table longs more then 1 second!!. While queries produced by dbaccess, Business Objects are executed with normal speed.
May be you know any tools, methods, etc to monitor Ardent perfomance and find bottleneck?
Alexandre
RW> There is a limit (undocumented, but mentioned in the past on this
RW> list) of 8K bytes for any expression in DataStage. If its getting
RW> near this limit (say over 6K bytes, since column names are re-mapped
RW> when the expression is compiled), consider replacing the expression
RW> with a call to a Routine (transform function).
RW> In the "Advanced DataStage" class offered in Asia-Pacific region
RW> there is a module on the topic "Designing for Performance". This is
RW> the only resource of which I am aware.
RW> The main performance issues typically are external factors, such as
RW> available (rather than theoretical) network bandwidth, database
RW> server performance and hardware performance. Of course, inefficient
RW> coding practices in DataStage will never help!
RW> -----Original Message-----
RW> From: Alexandre Stoulov [mailto:alexs@tern.ru]
RW> Sent: Monday, 02 April 2001 18:24
RW> To: informix-datastage@oliver.com
RW> Subject: Some questions
Best regards,Alexandre Stoulov
------------------------------
TERN Technical Support
mailto:alexs@tern.ru
But this is very strange. The length of constraints is about 1K. The condition is simle, it check the equality of string in DB and inut string and works wrong (debuger shows identical values, Ardent considers conversly).
I dontt think that in our case (Sun Enterprise 3500, 2Gb Ram,
IDS.2000) performance is determined by external factors. The simple row update in the 50000 records table longs more then 1 second!!. While queries produced by dbaccess, Business Objects are executed with normal speed.
May be you know any tools, methods, etc to monitor Ardent perfomance and find bottleneck?
Alexandre
RW> There is a limit (undocumented, but mentioned in the past on this
RW> list) of 8K bytes for any expression in DataStage. If its getting
RW> near this limit (say over 6K bytes, since column names are re-mapped
RW> when the expression is compiled), consider replacing the expression
RW> with a call to a Routine (transform function).
RW> In the "Advanced DataStage" class offered in Asia-Pacific region
RW> there is a module on the topic "Designing for Performance". This is
RW> the only resource of which I am aware.
RW> The main performance issues typically are external factors, such as
RW> available (rather than theoretical) network bandwidth, database
RW> server performance and hardware performance. Of course, inefficient
RW> coding practices in DataStage will never help!
RW> -----Original Message-----
RW> From: Alexandre Stoulov [mailto:alexs@tern.ru]
RW> Sent: Monday, 02 April 2001 18:24
RW> To: informix-datastage@oliver.com
RW> Subject: Some questions
Best regards,Alexandre Stoulov
------------------------------
TERN Technical Support
mailto:alexs@tern.ru