Feb 15, 2023 07:37
1 yr ago
21 viewers *
English term
expensive queries
English to Chinese
Tech/Engineering
IT (Information Technology)
The cluster setting to allow expensive queries is off, so some features are disabled.
请问什么是expensive查询呢？谢谢！
请问什么是expensive查询呢？谢谢！
Proposed translations
(Chinese)
| 5 | 消耗系统资源多的查询 |
jyuan_us
|
| 4 +1 | 比较耗费资源的查询 |
Frank Feng
|
| 5 | 定位消耗系统资源多的查询 |
Bruce Guo
|
Proposed translations
5 mins
Selected
消耗系统资源多的查询
消耗系统资源多的查询（以下简称为 expensive query）
耗费较多资源的查询
https://docs.pingcap.com/zh/tidb/dev/identify-expensive-quer...
--------------------------------------------------
Note added at 22 hrs (2023-02-16 06:17:01 GMT)
--------------------------------------------------
直译为“成本高的查询”也未尝不可。可以把英文用括号后缀在后边: “成本高的查询”(expensive query)
耗费较多资源的查询
https://docs.pingcap.com/zh/tidb/dev/identify-expensive-quer...
--------------------------------------------------
Note added at 22 hrs (2023-02-16 06:17:01 GMT)
--------------------------------------------------
直译为“成本高的查询”也未尝不可。可以把英文用括号后缀在后边: “成本高的查询”(expensive query)
3 KudoZ points awarded for this answer.
Comment: "我用的是“资源密集型查询”，谢谢！"
+1
2 mins
Frank Feng
China
China
Native in Chinese
Specializes in field
China
Financial, Medical, Game, IT Translation
Native in: Chinese (Variants: Simplified, Mandarin, Traditional) , Mandarin Chinese 
Works in: English to Chinese, Chinese to English, English to Mandarin Chinese
Related KudoZ points
:
2175
比较耗费资源的查询
指需要消耗比较多计算资源的查询（比如涉及更多数据源、更多数据量、更多关联操作等等）
9 mins
定位消耗系统资源多的查询
Expensive queries are database queries that run slowly and/or spend a significant amount of their execution time reading and writing to disk. Such queries are the most common cause of performance issues on Heroku Postgres databases.
Optimizing expensive queries can significantly improve your application’s performance and overall response times.
Optimizing expensive queries can significantly improve your application’s performance and overall response times.
Reference:
https://devcenter.heroku.com/articles/expensive-queries
https://docs.pingcap.com/zh/tidb/dev/identify-expensive-queries
Something went wrong...