Memory usage after initializing SessionFactory

[danilosingh]

We have a desktop application with 470 entities. The problem is that the application consumes more around 150MB in memory just when initializing the application, and of course this increases as the user uses. We have a long-term concern because this domain will grow.
We have clients that use Terminal Service, with many users, and our infrastructure reality in Brazil is precarious, which has generated problems of slowness in the system.
Is it possible to do something to decrease memory consumption at startup?
It would be great if Nhibernate created all the necessary configuration (loaders, proxies, sql strings) only in the first use of the entity, although this means to lose some performance in the first access.
Has anyone ever had this kind of problem? Do you know a strategy to improve?

[namer315]

We have the same issue
is there any way to load entities per use only and have the ability dispose them later on
Thanks in advance

[fredericDelaporte]

Related to #1904.

It was about lazy initializing some of the memory consuming data, but due to the bad impact it would have on warm-up (for example for server farms which do application warm-up on newly brought up instances before actually adding them to the farm), it was concluded:

Better to optimize the code in batchers instead.

[danilosingh]

@fredericDelaporte Could not this be optional?

[fredericDelaporte]

In fact, duplicate of #1316.