caching - ASP.NET - Cache & Filter or SQL w/ a large results set? -
caching - ASP.NET - Cache & Filter or SQL w/ a large results set? -
i have big set of relatively static info (50,000+ rows) needs accessed .net mvc application on regular basis. each phone call info needs 5-20 rows @ time - filtered on 1 or 2 columns (usually "starts with" filter.)
i'm trying determine if has info on performance benefits of using filtered .net dataview (rowfilter) cached vs. hitting database each time. saves database - how efficient filtered dataviews? putting undue stress on web server?
a cache should used small, frequently-accessed bits of data, when same info required on , over. since getting different rows each time big dataset, bet database faster @ rummaging through 50,000+ rows couple of rows if table indexed. best way tell fire proof-of-concept both approaches , compare speed , amount of memory used between 2 approaches, , justice whether each falls in line requirements.
hope helps!
asp.net-mvc caching
Comments
Post a Comment