I am reading the beginning CHDB book and a line that confuses me a bit:
It is also worth noting that CouchDB will never overwrite existing documents, rather it will attach a new document to the attention of the latest document and others archived for archival purposes.
Does not mean that after some updates, you will have a large database? Thanks!
The short answer is "Not really, no"
In reality your documents Depends on the average size and quantity of them. It will define why you should run a compact work on your database, which is a job that removes all previous modifications from the database. For this, read more about coincidence at another sysadmin point, try to schedule your compaction jobs when the database is not under load. You care about writing most especially the weight, because if writing is going very fast, when you run the composition, your compaction job (in principle) can always run and take the database with it. . However, I have seen some good behaviors around the coincidence under a heavy reading load. Therefore, if you can do compacting only once a day, then do it with your system / database maintenance at 3:00 p.m. cron jobs.
Oh, and most importantly, if you are just starting to learn Coachbub, then you may start worrying about running your compaction jobs against your system's load. Periodic adaptation and all that - now focus on other aspects.
Cheers.
Comments
Post a Comment