S
Shabam
Suppose in a .net application a user sees his homepage, which includes many
elements the requires sql queries. Each user sees a different homepage
obviously. Executing these queries every time a user goes to his homepage
is obviously going to drain a lot of systems resources, especially since
most of the time it's the same.
What are some of the ways to make this efficient? Perhaps some sort of
caching mechanism, or even a temporary table that stores just the elements
needed for display in the homepage?
elements the requires sql queries. Each user sees a different homepage
obviously. Executing these queries every time a user goes to his homepage
is obviously going to drain a lot of systems resources, especially since
most of the time it's the same.
What are some of the ways to make this efficient? Perhaps some sort of
caching mechanism, or even a temporary table that stores just the elements
needed for display in the homepage?