Best practice for working with data in memory

Question

0.00/5 (No votes)

See more:

Hi Guys

I would like to know what would be the best practice in .net for the following

I currently have a .net application which i am busy with and just would like to know what would be the best practice of handling the data.

Currently on page load i have some data that gets loaded into a datatable which is used as the datasource for a datagrid.

in the grid there is a link which the user clicks which redirects them to a calculation page and once completed on the calculation page, the application redirects to the previous page and i pass the calculation back to the previous page through a datatable in a viewstate.

Is this the best way or is there a better way of handling this?

What I have tried:

currently i pass a session variable which holds a uniqueId for the row being updated, to the calculation page once the calculation is done i have a viewstate which holds a datatable with the uniqueid and update the fields in the datatable and on redirect do a select on the viewstate datatable to see if the data exists for the rowId = uniqueid and update the columns in the datagrid if there is data

Posted 10-Jul-17 20:24pm

IsiR_19

Updated 10-Jul-17 20:32pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2017-07-10T20:32:00

The solution is fine. Memory managment gets only a problem, when the loaded data gets to big. First hints is: when it gets slower than normal.

If you want to preserve memory than check that you arent copying data around. Compute once and store the results in class data members. Miminize log and debug output.

Consider closing the db-connection after fetching the data. This is good resource managment.