[fdo-users] RE: How to boost ISelect and IUpdate command performance

Traian Stanev traian.stanev at autodesk.com
Tue Nov 30 15:49:21 EST 2010

If there is no performance gain from this and your performance is still slow, it means that you have a bigger bottleneck somewhere in the pipeline. It would help if you gave more information about what type of data source you are using and what your performance expectation is -- e.g. it would be unrealistic to expect 10 million queries per second with, say, WFS data.


> -----Original Message-----
> From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-
> bounces at lists.osgeo.org] On Behalf Of Ray
> Sent: Tuesday, November 30, 2010 3:15 PM
> To: fdo-users at lists.osgeo.org
> Subject: [fdo-users] RE: How to boost ISelect and IUpdate command
> performance
> I tried both Romy and Traian's solution.
> Romy's solution doesn't work. The SelectCmd.ParameterValues returns me
> nothing and it is read only. I guess autodesk fdo for Oracle doesn't
> support
> this.
> Taian's solution works. However, it doesn't have any performance gain.
> It
> has exactly the same performace as the filter string is bound to
> selectCmd
> in every call.
> --
> View this message in context: http://osgeo-
> org.1803224.n2.nabble.com/How-to-boost-ISelect-and-IUpdate-command-
> performance-tp5788379p5789506.html
> Sent from the FDO Users mailing list archive at Nabble.com.
> _______________________________________________
> fdo-users mailing list
> fdo-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users

More information about the fdo-users mailing list