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.
What is the impact of creating variables using:
Dim ds as New DataSet
ds = GetActualData()
where GetActualData() also creates a New DataSet and returns it?
Does the original empty DataSet that was ‘New’ed just get left in the Heap?
What if this kind of code was in many places? Would that affect the ASP.NET process and cause it to recycle sooner?
The impact is that you are creating more objects than you need to.
The unused object will be left on the heap, so it will need to be garbage collected eventually. If you do this a lot, it will result in the garbage collector having to run more frequently.
Compared to the real work done it should however be minimal, i.e. actually populating a data set is so much more work that the extra unused object is almost negligible.
It won’t cause the ASP.NET process to recycle sooner, as object throughput / GC frequency is not a factor.
Eventhough the impact is minimal, the code should of course not create those unused objects. Perhaps more important than the performance is that the code doesn’t really correspond with what you want to accomplish. Every little discrepancy like that makes the code harder to maintain.