Hello:
> AFAIK you don't create more objects. Is exactly the same, the
> difference is that instead of making thousands of calls to GetEncoding
> , and going several times through the switch statement, you just do it
> once... We didn't detect a hit on memory consumption (I will double
> check)
Hello:
> Well, we have run our internal tests, and also the profiler, and changing =
> this code gains 20%, so it doesn't seem to be doing exactly the same. The =
> "old" code running through the switch several times, and creating an =
> encoding object thousands of times too.
> Our tests run our
> Well, we have run our internal tests, and also the profiler, and changing
> this code gains 20%, so it doesn't seem to be doing exactly the same. The
> "old" code running through the switch several times, and creating an
> encoding object thousands of times too.
Well, I meant the same in terms o
<[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2007 1:38 AM
Subject: Re: [Firebird-net-provider] Big performance gain on Charset.cs
>> AFAIK you don't create more objects. Is exactly the same, the difference
>> is that instead of making thousands of calls to GetEncoding , and going
&
Hello:
> So, at least for the normal framework, doing it once in the constructor is
> the same as doing it each time it is used (in terms of the behavior).
I can try to check it in the changelog but if i remember well, that
change was done time ago on a user request for that reason ( i maybe
wr
> AFAIK you don't create more objects. Is exactly the same, the difference
> is that instead of making thousands of calls to GetEncoding , and going
> several times through the switch statement, you just do it once... We
> didn't detect a hit on memory consumption (I will double check), but
> pefor
lvarez" <[EMAIL PROTECTED]>
Cc: "For users and developers of the Firebird .NET providers"
Sent: Monday, April 16, 2007 12:59 PM
Subject: [Firebird-net-provider] Big performance gain on Charset.cs
> Hi all,
>
> We are heavily relying on Firebird for our versi
Hello:
> Afaik, the behaviour is still right, but performance is about 20% better.
The only problem with that will be with the amount of memory used by the
charsets if we do that in tha way.
As it's now there will be Encoding instances on ly in the charsets that
are being used, while if we do
Hi all,
We are heavily relying on Firebird for our version control product, Plastic
SCM, and we have just found a big performance boost making a small change on
Charset.cs.
On our tests we have reduced overall time around 20% just changing the
following on Charset.cs, so we thought you might b
