Activator.CreateInstance and beyond

re: Activator.CreateInstance and beyond

Peli — Fri, 18 Nov 2005 10:46:34 GMT

Aren't you on vacation ? :)

re: Activator.CreateInstance and beyond

Alam — Wed, 15 Feb 2006 21:31:11 GMT

The code seems to be just like psudo code. Can you please explain those codes better? I understand the issue ir comparing, not teaching how it is done. For instance, for dynamic method one, what are the parameters you pass in and how it is actually working???

Thanks

re: Activator.CreateInstance and beyond

Jeff — Fri, 21 Jul 2006 00:05:57 GMT

My result show a different story. My "Parameter" test have a smiliar result to the "Parameterless" test, ie: DynamicMethod+Delegate approach is 10 times faster than "Activator.CreateInstance" approach.

I don't quite believe that with parameter, it jump from less than 6 second to almost 9.5 minutes(568 seconds). Something is not quite right. Could you please post your testing source code? Thanks.

re: Activator.CreateInstance and beyond

Haibo_Luo — Fri, 21 Jul 2006 05:43:31 GMT

Please find the code here: http://blogs.msdn.com/haibo_luo/articles/494008.aspx.
At that time, the community server did not support attachment.

re: Activator.CreateInstance and beyond

Jeff — Fri, 21 Jul 2006 17:42:15 GMT

Thanks. What do I do with the perl code?

re: Activator.CreateInstance and beyond

Jeff — Mon, 24 Jul 2006 18:53:05 GMT

Ok, you are right. I wasn't running 2000 types. Thanks, great help.

Activator::CreateInstance performance for more than 16 types == baaaaad

hacked.brain — Fri, 15 Sep 2006 02:29:24 GMT

Activator.CreateInstance speed

Rory Primrose — Mon, 04 Dec 2006 03:50:26 GMT

This is another one of those memory (as in I want to keep some kind of reference to this post) type of

Singleton provider at THE COLUMN

Singleton provider at THE COLUMN — Fri, 08 Dec 2006 02:59:26 GMT

PingBack from http://www.thecolumn.dk/2006/12/08/c/singleton-provider/

re: Activator.CreateInstance and beyond

Jeff Gonzalez — Thu, 01 Feb 2007 09:11:32 GMT

If it is the same type you are calling over and over, you can implement IClonable().

Then you could call Activator.CreateInstance once, store the result in a hashtable and use it to get a blank copy of the type.

You don't incur the Activator.CreateInstance penalty after the initial run.

反射，我们需要知道什么？

小春 — Fri, 20 Jul 2007 19:00:34 GMT

我们在项目中经常用哪种方式来反射方法来创建实例，调用指定的方法和属性？它们的性能怎么样？本文收藏了国外上面一些优秀的文章，仅供参考。

Reshef’s tip of the day » Blog Archive » Reflection and performance: DynamicMethod

Mon, 17 Dec 2007 14:07:44 GMT

PingBack from http://jajahdevblog.com/reshef/?p=26