Hi. I've already reply to this on the other discussion.
Thank you Fabio.
RP
On 3 Set, 15:35, Fabio Maulo wrote:
> Ricardo,Can you explain which is the real life use-case where you need to
> upload 100K entities ?
> Or your intention is only waste time in something you never need ?
>
> 2009/9/3
Ricardo,Can you explain which is the real life use-case where you need to
upload 100K entities ?
Or your intention is only waste time in something you never need ?
2009/9/3 Ricardo Pedro
>
> There is a similir discussion here:
>
> http://groups.google.com/group/nhusers/t/36b822f448c46b8b
>
> BTW
There is a similir discussion here:
http://groups.google.com/group/nhusers/t/36b822f448c46b8b
BTW: I'm thrileed that there is now a big discussion and comparison
between NH and EF.
This should lead to a big improvement in NH, and as an OpenSource big
FAN this is what NH is needing now.
NH is a
Hi to all.
I can add some more information about this:
The big diference between NH and EF are in the "materialize" or
"hidrate" time!
I don't have the solution for this, but I can add more information to
try solving it...
I run the jetBrains dot Trace, and what I found was the Hidrate method
"F.B. ten Kate" writes:
[session vs. stateless session]
> Well wouldn't NHibernate be slow _every_ time i run this query then?
Not necessarily. I don't know the exact overhead, but the default,
stateful session uses caching mechanisms, so maybe filling the cache
is slow.
I would also suspect, a
return entiteit;
> > > > > }
> > > > > }
> > > > > public virtual Int32 ActiefNeeJa
> > > > > {
> > > > > set
> > > > > {
> > > >
> > actiefneeja = value;
> > > > }
> > > > get
> > > > {
> > > > return actiefneeja;
> > > > }
> > > > }
> > > > p
t; > name = value;
> > > }
> > > get
> > > {
> > > return name;
> > > }
> > > }
> > > public virtual string Sorteernaam
> > >
gt; > get
> > {
> > return name;
> > }
> > }
> > public virtual string Sorteernaam
> > {
> > set
> > {
> > sorteernaam = value;
If you are "playing" starting from a "button click" (as you said) I sure you
are doing more than one thing wrong with both NH and EF.Btw use what is more
easy to use for your needs without waste so much time testing only the
upload of 39 entities (that mean testing something you will never gonn
}
> }
> public virtual DateTime DatumWijziging
> {
> set
> {
> datumwijzigen = value;
> }
> get
> {
> return datumwijzigen;
> }
>
f you show us your configuration file and mapping files we can help
> more.
>
> -Carlos
>
> Practice makes perfect, but if no one is perfect, why practice?
>
> > Date: Wed, 12 Aug 2009 05:26:29 -0700
> > Subject: [nhusers] Re: NHIbernate performance vs Entity Framework
&g
Maybe if you show us your configuration file and mapping files we can help more.
-Carlos
Practice makes perfect, but if no one is perfect, why practice?
> Date: Wed, 12 Aug 2009 05:26:29 -0700
> Subject: [nhusers] Re: NHIbernate performance vs Entity Framework
> From: folk...@bl
Well i'm justing "playing" around to justify us going for NHibernate
or EF as our ORM. Personally from what i've read i'd prefer NHibernate
but when basically just trying to retrieve the same amount of records
in both tech's (trying to see which is easier to understand and
supports the features we
which is the target of what you are doing ?
2009/8/12 F.B. ten Kate
>
> Well wouldn't NHibernate be slow _every_ time i run this query then?
> if it has to create the objects? After all it has no problems doing so
> the 2nd time i click the button. Also afaik EF also has to create
> these object
Well wouldn't NHibernate be slow _every_ time i run this query then?
if it has to create the objects? After all it has no problems doing so
the 2nd time i click the button. Also afaik EF also has to create
these objects.
I'm willing to give the stateless session a try though, how would i
implemen
I saw a similar thread sometime back in this forum where it was a
similar issue. the query was fast but NH was taking long time to
create the entities (there was a large number of entities being loaded
in the same query).
I dont remember the outcome of the discussion but I remember some
suggestion
Forgot about the profiler question,
When i say duration i'm looking at the SQL:BatchCompleted row, which
with my limited SQL Profiler knowledge shows the time it took the SQL
to execute in the "Duration" field.
On 12 aug, 14:29, "F.B. ten Kate" wrote:
> I'm not running a specific test, i'm si
I'm not running a specific test, i'm simply "implementing" in a quick
dummy project, like i said this is to get used with NHibernate some
and things. I can show you the two mappings that i have though.
Changed the code a little, i'm now creating one session, and one
factory on the Load. However i use a button_click to trigger the
actual querying..
First time i click el button it's slow (both the msgbox timer shows 21
seconds and profiler tells me 19 seconds) but the second time i hit
the button
Would you mind
1 - Sharing the smallest bit that reflects the problem as a whole ( your
code under test, your tests, and mappings)
2 - Running a code profiler and share the screenshot of it (to pinpoint the
bottleneck)?
And a question, when you are talking about the times in sql profiler, do you
Ow, little extra info, it's 39 Records i'm querying, which
obviously is kinda alot.
On 12 aug, 14:12, "F.B. ten Kate" wrote:
> Like i said, the "timer" is in SQL Profiler. In otherwords not in the
> code, but i also have the following bits in there to compare.
>
> DateTime start
Like i said, the "timer" is in SQL Profiler. In otherwords not in the
code, but i also have the following bits in there to compare.
DateTime start = DateTime.Now;
IList lijst = session.CreateCriteria(typeof
(Debiteur)).List();
DateTime stop = DateTime.Now;
The sql is not executing slowly, the building of the sessionfactory is
slow. Start your timer after buildsessionfactory and compare again.
On Wed, Aug 12, 2009 at 2:01 PM, F.B. ten Kate wrote:
>
> Yes i am atm, since it's just a quit check to run a query, but would
> this explain the SQL executin
Yes i am atm, since it's just a quit check to run a query, but would
this explain the SQL executing this slowly?
I know i'm not using any "best" practises and things, this is the
first thing im doing with both NHibernate and EF.
Here is the code running it.
Configuration cfg = new C
Are you creating a new SessionFactory each run? (SLOOOW!!!)
You should use a single instance SessionFactory and just create new
sessions.
F.B. ten Kate wrote:
> Hello there, im currently looking at some differences between both
> ORM's and to get a good feel for both i try to query from
26 matches
Mail list logo
