Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If .Count or .Count() is used several times on objects that implement ICollection (therefore with O(1) computational complexity, unless of course it has been overriden), is it better performance-wise (not memory wise), even for a very small difference, to cache the value in a temporary variable rather than accessing the property value each time it is needed?
Yes, it could be (very slightly) faster, since the overhead of a method call, associated error checking, and (in the case of Count()) the dynamic type checking for ICollection have some amount of overhead.
Is it worth it though? That’s entirely up to you and your application. If you’re in a very tight inner loop, it might be worth it. Then again, on more recent .NET runtimes, this sort of trivial property will probably get inlined in such circumstances.
As always, let your profiler tell you where the hotspots are in your application.