There was a fix I did a few years ago when the validator was passing the schema xsd file directly rather than producing a SchemaCollection object and passing that - meant that we were validating our schema for every mapping which had a large impact on both performance and peak memory consumption.
Reason I remember it was that running NHibernate test suite the process took 650Mb though there were no obvious memory leaks - turns out .NET doesn't give the memory back to the OS unless you hit the memory high watermark limit Paul On Nov 24, 11:47 am, Fabio Maulo <[email protected]> wrote: > Try to remove it and let me know. > > 2009/11/24 Ayende Rahien <[email protected]> > > > > > > > That is funny, IIRC, the most expensive part in creating configuration _is_ > > the schema validation. > > > On Sun, Nov 22, 2009 at 8:28 AM, Fabio Maulo <[email protected]> wrote: > > >> Only as info. > >> I have tried to disable the schema validation loading mappings. > >> As quick test I have used our test suite where we are loading some hundred > >> of mappings without see any significant difference. > > >> In practice disabling the schema validation does not give any > >> performance improvement and, if we disable it, try to find a possible the > >> cause of an exception will be a "nice" challenge. > > >> Can you confirm the non-existence of performance improvement ? > > >> Thanks. > >> Fabio Maulo > > -- > Fabio Maulo- Hide quoted text - > > - Show quoted text -
