・フィールドが大量にある場合のパフォーマンスについて
とあるアプリの設計中です。必要なフィールド数を試算したところ，少なくとも 35000 以上必要であることが分かりました。
1ドキュメントでこれらのフィールド全てを使うわけではありません。1ドキュメントで，最大で300フィールド使用され，残りの 34700 フィールドは使用しません。
このような使い方は検索やソートなどのパフォーマンスに影響するでしょうか？もし影響するのならどのような代替案が考えられるでしょうか？
評価
50
翻訳 / 英語
- 2018/05/10 20:25:37に投稿されました
Performance if there is a large volume of field
I am designing an application. I calculated the number of the necessary field as trial, and found that I need at least more than 35000.
I do not use all these fields in 1 document. I use 300 field in 1 document at maximum, and do not use remaining 34700 fields.
Does this way of using it affect performance such as retrieving and sorting? If it is affected, what kind of alternative idea do we have?
issei2029さんはこの翻訳を気に入りました
I am designing an application. I calculated the number of the necessary field as trial, and found that I need at least more than 35000.
I do not use all these fields in 1 document. I use 300 field in 1 document at maximum, and do not use remaining 34700 fields.
Does this way of using it affect performance such as retrieving and sorting? If it is affected, what kind of alternative idea do we have?
評価
52
翻訳 / 英語
- 2018/05/10 20:24:45に投稿されました
・With regard to the performance in the event of a large number of fields
A particular application is currently being designed. When the number of required fields was calculated, it became known that we would need to have at least more than 35,000 fields.
It is not possible for one document to use all these fields. In one document, the maximum number of fields to be used is 300 while the remaining 34,700 fields will be untouched.
For an usage method like this, will having a search or sort function affect the performance? If there is some effect, is there any alternative solution which can be applied.
issei2029さんはこの翻訳を気に入りました
A particular application is currently being designed. When the number of required fields was calculated, it became known that we would need to have at least more than 35,000 fields.
It is not possible for one document to use all these fields. In one document, the maximum number of fields to be used is 300 while the remaining 34,700 fields will be untouched.
For an usage method like this, will having a search or sort function affect the performance? If there is some effect, is there any alternative solution which can be applied.
評価
50
翻訳 / 英語
- 2018/05/10 20:44:35に投稿されました
・ About a performance when a field is huge
I am designing a certain application about a performance when a field is huge.
It was understood that more than at least 35000 was necessary when the number of necessary field was calculated as a test.
All these fields were not employed in one document.
In one document, it was used 300 fields at the maximum, and 34700 remaining fields were not used.
Will such usage influence performances such as a search or the sort?
What kind of substitute plan will be thought about if it is influenced?
issei2029さんはこの翻訳を気に入りました
I am designing a certain application about a performance when a field is huge.
It was understood that more than at least 35000 was necessary when the number of necessary field was calculated as a test.
All these fields were not employed in one document.
In one document, it was used 300 fields at the maximum, and 34700 remaining fields were not used.
Will such usage influence performances such as a search or the sort?
What kind of substitute plan will be thought about if it is influenced?
・1つのクエリでhogeに出現する値を一括変換
employee_name というフィールドを作成し，それをhoge属性としています。
ここで，フィールドの値の一部であるMr.SmithがMr.Brownに変更になったとします。Mr.Smithが仮に100万ドキュメントに出現していたら，100万個の削除クエリと更新クエリを発行する必要があるのでしょうか？
1個のクエリで済む簡便な更新方法はないでしょうか？
評価
50
翻訳 / 英語
- 2018/05/10 20:32:36に投稿されました
Convert values appearing on hoga all together by using 1 query
I create a field called employee_name, and use it as attribute of hoga.
If Mr.Smith that is part of the value of the field is changed to Mr.Brown, do I have to issue 1 million deletion queries and updating queries in case where Mr.Smith appears in 1 million documents?
Do we have a simple way of updating to use only 1 query?
issei2029さんはこの翻訳を気に入りました
I create a field called employee_name, and use it as attribute of hoga.
If Mr.Smith that is part of the value of the field is changed to Mr.Brown, do I have to issue 1 million deletion queries and updating queries in case where Mr.Smith appears in 1 million documents?
Do we have a simple way of updating to use only 1 query?
評価
52
翻訳 / 英語
- 2018/05/10 20:28:59に投稿されました
・Doing a batch conversion for the values which appear in the hoge when running a single query
A file by the title of employee_name has been created with hoge attributes.
In this file, a portion of the field values has to be changed from Mr.Smith to Mr.Brown. Assuming if Mr.Smith appears in a million documents, do we have to create a million clear-and-remove queries to carry out the change? Is there a simple method to do this in one query?
issei2029さんはこの翻訳を気に入りました
A file by the title of employee_name has been created with hoge attributes.
In this file, a portion of the field values has to be changed from Mr.Smith to Mr.Brown. Assuming if Mr.Smith appears in a million documents, do we have to create a million clear-and-remove queries to carry out the change? Is there a simple method to do this in one query?
