A Paging Strategy -


i have lots of statistical reports, each of them contains 20000 records or more. gui dispaly these results paging 1000 records 1 page, when server calculated results using data db, server should stored results in db/memory/file support paging. these methods not when there lots of requests gui. there paging strategy solve problem. appreciated!

well, paging , can use startrow , endrow narrow down range. indexing columan can accelerate query. if application upate data in db frequently, it's not idea save query result in cache of them outdated soon. 1 way resolve high concurrent scenario using connection pool.


Comments

Popular posts from this blog

c++ - Is it possible to compile a VST on linux? -

java - Output of Eclipse is rubbish -

jquery - Confused with JSON data and normal data in Django ajax request -