Here are the results of a quick speed test comparing the configuration code in the latest release compared to the code in the SVN repository:
http://www.mail-archive.com/user-cs%40ibatis.apache.org/msg00178.html My tests on my machine shows the new code is about an order of magnitude faster than the last release: http://micro.magnet.fsu.edu/primer/java/scienceopticsu/powersof10/ The code in SVN does not use the XmlSerializer. --- Okku Touronen <[EMAIL PROTECTED]> wrote: > Hello I have been using iBatis for Java and we have a product > management > system up and running. But due to some economical reasons we are > about to > change to .NET instead. > > > > I have been toying around with iBatis for .NET for two days and have > a > simple application up and running with only a simple sqlMap with 4 > properties. > > > > But I have noticed that it takes up to 8 seconds for iBatis to run > the > Configure for this simple solution. > > > > When I profile there have been 33 calls to > System.Xml.Serialization.XmlSerializer..ctor(class System.Type) > taking 7,675 > s. > > > > How does this scale? In our product management system we have about > 50 > sqlMaps, some maps really big 30KB. > > > > Yes I know this is a one time penalty but it just don't feel right. > > > > Any clues? > > > > Regards Okku Touronen > >
