MethodInfo Invoke, bad performance?
-
I use the MethodInfo Invoke() Method. The Invoked Method is a drawing routine. Is it right that the MethodInfo Invoke() Method is extremly slow?
Compared to a direct call, yes, it's very slow. What are you trying to do, and can you do it with an interface? Making calls through interfaces is fast.
-
I use the MethodInfo Invoke() Method. The Invoked Method is a drawing routine. Is it right that the MethodInfo Invoke() Method is extremly slow?
STW wrote: I use the MethodInfo Invoke() Method. The Invoked Method is a drawing routine. Is it right that the MethodInfo Invoke() Method is extremly slow? Someone once said that if you need to ask how big is the cost of Reflection, you can't afford it. But there are much faster alternatives, like interfaces or delegates. Acting as a substitute for God, he becomes a dispenser of justice. - Alexandre Dumas
-
Compared to a direct call, yes, it's very slow. What are you trying to do, and can you do it with an interface? Making calls through interfaces is fast.
I thought I had an "extremly cunning plan" but hope you can tell me a better solution: I'm programming a little game with a lot of UserControls. These UserControls are filled with Data. But I don't like to pass DataAccess references to all of these Controls, so I thought I do it like in C++. MFC C++ Prgs are splitted in UI Views and Documents. Each View can have a document. From this document it's very simple to update the views (GetDocument().UpdateView(Name)) with new data. In this scenario I wouldn't have to pass references to the DataSet; I just have to programm a document class which handles adding Document Items (Controls, which are "listening" to changes of the document) and the Controls Update Methods. I made it like this: object array for the document items String array for the Update Method Name of the Control DocumentType, so I can Update only specific controls. MyDocument.AddDocumentItem(this.AreaControl1, "AreaCtrlUpdate", DocumentTypes.AreaControl) The Document has a DataSet and properties. So when the documents data changed with the set method of a property this will Update my Document Items. To Invoke a Method of a object I needed MethodInfo.Invoke() Method. Each DocumentItem have to implement a method like CtrlUpdate(Document pDoc). I add as a passing parameter of the CtrlUpdate method the Document itsself. What I found very good was first that Data is only stored at one place (in the document) and there is even no need to store IDs in the UserControls. Second there's no need to pass DataSet or DataAccess Object References because the DataSet is passed with the Document to the Controls Update Method. In the document I fix which Controls to Update if a property or the dataset changed. That's good because I can fix which Controls to update at only one place, in the document and there's no need that a control has object references to other controls which have to actualisize when the data was changed by the control. I just set the new property in the document and this will cause the Update Method of the other Controls. I made a mistake and so I meant that MethodInfo.Invoke() is very slow (Seconds to Invoke). So what do you mean with calling Methods through an interface? Is there a better solution for this scenario? Could you give me an example? I think about to use databinding with these UserControls but I couldn't find examples how to set a datasource, datamember for a UserControl. Do you know how to set datasource of usercontrols? Thank you! Stefan
-
STW wrote: I use the MethodInfo Invoke() Method. The Invoked Method is a drawing routine. Is it right that the MethodInfo Invoke() Method is extremly slow? Someone once said that if you need to ask how big is the cost of Reflection, you can't afford it. But there are much faster alternatives, like interfaces or delegates. Acting as a substitute for God, he becomes a dispenser of justice. - Alexandre Dumas
-
I thought I had an "extremly cunning plan" but hope you can tell me a better solution: I'm programming a little game with a lot of UserControls. These UserControls are filled with Data. But I don't like to pass DataAccess references to all of these Controls, so I thought I do it like in C++. MFC C++ Prgs are splitted in UI Views and Documents. Each View can have a document. From this document it's very simple to update the views (GetDocument().UpdateView(Name)) with new data. In this scenario I wouldn't have to pass references to the DataSet; I just have to programm a document class which handles adding Document Items (Controls, which are "listening" to changes of the document) and the Controls Update Methods. I made it like this: object array for the document items String array for the Update Method Name of the Control DocumentType, so I can Update only specific controls. MyDocument.AddDocumentItem(this.AreaControl1, "AreaCtrlUpdate", DocumentTypes.AreaControl) The Document has a DataSet and properties. So when the documents data changed with the set method of a property this will Update my Document Items. To Invoke a Method of a object I needed MethodInfo.Invoke() Method. Each DocumentItem have to implement a method like CtrlUpdate(Document pDoc). I add as a passing parameter of the CtrlUpdate method the Document itsself. What I found very good was first that Data is only stored at one place (in the document) and there is even no need to store IDs in the UserControls. Second there's no need to pass DataSet or DataAccess Object References because the DataSet is passed with the Document to the Controls Update Method. In the document I fix which Controls to Update if a property or the dataset changed. That's good because I can fix which Controls to update at only one place, in the document and there's no need that a control has object references to other controls which have to actualisize when the data was changed by the control. I just set the new property in the document and this will cause the Update Method of the other Controls. I made a mistake and so I meant that MethodInfo.Invoke() is very slow (Seconds to Invoke). So what do you mean with calling Methods through an interface? Is there a better solution for this scenario? Could you give me an example? I think about to use databinding with these UserControls but I couldn't find examples how to set a datasource, datamember for a UserControl. Do you know how to set datasource of usercontrols? Thank you! Stefan
Here's what I suggest: Define an interface: interface IDocumentItem { void CtrlUpdate(Document pDoc); } and then implement it in each of the DocumentItem classes. Then, when you want to do the update, you can cast the DocumentItem to an IDocumentItem, and then call CtrlUpdate() through that reference. That will be fast fast. Does that make sense?
-
Here's what I suggest: Define an interface: interface IDocumentItem { void CtrlUpdate(Document pDoc); } and then implement it in each of the DocumentItem classes. Then, when you want to do the update, you can cast the DocumentItem to an IDocumentItem, and then call CtrlUpdate() through that reference. That will be fast fast. Does that make sense?