现在dataworks负载很大吗?API接口一直超时,[INFO] [11:07:00.121] resource group is 0[INFO] [11:07:00.143] prepared test environment, take time 449 ms[INFO] [11:07:00.158] api context init , take time 2 ms
[INFO] [11:07:00.158] start to test api[416180068299458]: 查询指定商家销售明细
[INFO] [11:07:00.158] test case parameters:
[INFO] [11:07:00.159] QUERY:[{"paramKey":"pageNum","paramValue":"1"},{"paramKey":"pageSize","paramValue":"10"},{"paramKey":"projectCode","paramValue":"3300"},{"paramKey":"beginTime","paramValue":"20230724"},{"paramKey":"endTime","paramValue":"20230724"},{"paramKey":"supplierIds","paramValue":""},{"paramKey":"storeIds","paramValue":"[239762091026673664]"},{"paramKey":"sortValue","paramValue":""},{"paramKey":"siteIds","paramValue":""}]
[INFO] [11:07:00.159] not use dynamic sql
[INFO] [11:07:00.160] api request execution started. [OK]
[INFO] [11:07:00.160] api sql realsql : SELECT supplier_id AS "supplierId", max(supplier_name) AS "supplierName", store_id AS "storeId" , max(store_name) AS "storeName", site_id AS "siteId" , max(site_name) AS "siteName" , round(SUM(day_gmv), 2) AS "gmv" , COALESCE(round(SUM(day_sales), 2), 0) AS "sales" , SUM(gmv_goods_sell_count) AS "gmvGoodsSellCount", SUM(sales_goods_sell_count) AS "salesGoodsSellCount" , SUM(gmv_order_count) AS "gmvOrderCount", SUM(sales_order_count) AS "salesOrderCount" FROM odps_wsnb_online_ds_dws_supplier_sales_detail WHERE project_code = '3300' AND time >= 20230724 AND time <= '20230724' AND store_id IN (239762091026673664) GROUP BY supplier_id, store_id, site_id ORDER BY gmv DESC
[INFO] [11:07:00.160] query database started. [OK]
[ERROR] [11:07:10.226] api request executed [FAILED]
[INFO] [11:07:10.227] api request executed, take time : 10069 ms
[WARN] [11:07:10.227] your query is too slow,please check sql and database
[INFO] [11:07:10.227] api test finished, take time 10071 ms
数据量大的确可能会导致API接口响应慢或超时。
主要的原因有几个:
数据量过大:表中的数据量或者查询出的数据量特别庞大,会导致API查询和返回数据变慢。
负载高峰:如果是近期DataWorks的访问量和查询量急剧增长,可能会暂时导致API接口的负载过高。
硬件配置:DataWorks和数据源的服务器配置(CPU、内存等)无法支撑大规模的API调用。
网络延迟:DataWorks和数据源(如MySQL)之间存在较高的网络延迟,延长API响应时间。
SQL效率低下:API对应的SQL查询效率较低,需要花费较多时间执行。
缺少索引:API查询的字段没有建立合适的索引,导致全表扫描。
系统故障:DataWorks后端API服务存在临时性的故障。
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。
DataWorks基于MaxCompute/Hologres/EMR/CDP等大数据引擎,为数据仓库/数据湖/湖仓一体等解决方案提供统一的全链路大数据开发治理平台。