Home/ Questions/Q 3360736
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T03:01:42+00:00

According to profiler it takes 24 sec for FluentConfiguration.BuildConfiguration to complete. Here’s the code

  • 0

According to profiler it takes 24 sec for FluentConfiguration.BuildConfiguration to complete. Here’s the code I use to get Configuration:

    MsSqlConfiguration persistenceConfigurer = MsSqlConfiguration
         .MsSql2005
         .ConnectionString(connectionStringBuilder => connectionStringBuilder
                                                      .Server(server)
                                                      .Database(database)
                                                      .Username(userName)
                                                      .Password(password))
         .ProxyFactoryFactory<ProxyFactoryFactory>()
         .CurrentSessionContext<ThreadStaticSessionContext>()
         .DoNot.ShowSql();

FluentConfiguration cfg = Fluently.Configure()
   .Database(persistenceConfigurer)
   .Mappings(m => m.FluentMappings.AddFromAssemblyOf<ExecutorMap>());

return cfg.BuildConfiguration();

The number of map-files is 19. Is it common for Fluent NHibernate to work so long? Might it be my fault? What could be wrong?
Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you’re using a profiler, you should be able to see what calls inside of BuildConfiguration are taking up that time. What are they?

    Assembly scanning would be my guess. Is the assembly that contains your mappings especially large? You’ve told Fluent NHibernate to scan your assembly for mappings, so regardless of how few mappings there are it still has to scan the entire assembly for them.

    • 0