View Optimization: Is there great differences?

I have a database with 50000 documents, currently it has around 30 views. I tried to have less view initially, but since my view display current month data and forecast data, which depends on what month I am currently, it take too long to refresh, about 30 minutes to one hour. This is because my columns displayed time dependant data. Thus, I am thinking to create many views instead, but the columns will not have time dependant data, and each view will only display certain documents, rather than all documents. However I read many view will slow down the database.

Thus, any real life experience is appreciated, which will give faster view refresh, one view, displayed 50000 documents, with many time dependant columns, or many views in database, say 24 view, i.e 2 different kind of documents selection, eg: Asia and Africa, but within Asia, one view for each month, ie 2 x 12 months = 24 months.

Which will give faster displayed of data?

Of course I can also have the time depandant in the form, but this will require me to refresh all 50000 documents, and lots of testing, which I don’t plan to do it for the time being.

any suggestion is appreciated.

Subject: View Optimization: Is there great differences?

Will, I would vote for number of views but if u can move your display of documents to embedded view(show single category) in a form categorized by months/region, will be an option to think about if their is no dependencies to show them in view.

:slight_smile:

Subject: RE: View Optimization: Is there great differences?

i like your suggestion, can you give some example how can the embedded view be dynamic?

Tq.