@gunter, interesting query and i am hearing it for the first time about the cpu consumption worries for the non indexed document type mutations. Perhaps- this is one area where we can look further on how to minimise/optimise the impacts out of such mutation noice in the buckets. There are already some long term plans for handling this.
What is the best strategy when creating FTS and bucket assignment?
Creating new bucket for every new FTS index ?
Not sure whether you are on an EE version of couchbase? Are you having MDS enabled/explicit FTS node?
If the cpu consumption is of really worrying magnitude then you may segregate all the FTS indexable data in a single bucket and then create a single FTS index with multi type mappings.
One bucket per FTS index may not scale well with more buckets/indexes.
Cheers!