No penalty until first request to a view. When a view is accessed, all documents updated since last request to the view are processed by the view code. More precisely, all views from the parent design document are applied to each updated doc, and their results are persisted.
So unless you use at least one of a design doc views at least once, the design doc‘s view cost is ~zero. However, first accessing a view in a DB with a lot of docs may seriously impact performance. ermouth пн, 23 сент. 2019 г. в 01:30, Jose Juan Montiel <[email protected] >: > Hi, > > the extended/explained title is: how much cost/increase views (in terms of > cpu, memory, storage) over only index, in the life of database/application. > > I know there are different things, for different targets, but i would like > to know how many things need to do the database, to keep its update with > new inserts. > > Some people propose in https://jira.hyperledger.org/browse/FAB-5528 to > include views in the smartcontract, but the mantainers decide to dismiss. > Now is possible create index, to accelerate the queries, but not possible > to aggregate info directly with view queries. > > The question its to know how much performance cold the blockchain loose if > views are created in couchdb. > > Thanks for all. > > -- > This is your badness level. > It's unusually high for someone your size. > We have to fix that. >
