无语的indexhint：手工分配哈希区，5小时不出结果，优化后20分钟-MySQL 튜토리얼-php.cn

집

데이터 베이스

MySQL 튜토리얼

无语的indexhint：手工分配哈希区，5小时不出结果，优化后20分钟

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 04:06 PM

분배하다

同事发来一个语句，说5个小时不出结果，我滴个神呀，想看看到底是什么垃圾语句造成的。于是叫同事发过来。不看不知道，一看吓一跳，3个表关联，强制使用了2个index hint，其中一个表9g，一个表67g，还有一个小表40Mb。无知的开发人员，以为走index就是快的，

同事发来一个语句，说5个小时不出结果，我滴个神呀，想看看到底是什么垃圾语句造成的。于是叫同事发过来。不看不知道，一看吓一跳，3个表关联，强制使用了2个index hint，其中一个表9g，一个表67g，还有一个小表40Mb。无知的开发人员，以为走index就是快的，哎。。。
下面是同事发来的语句： 
select /*+  parallel(t,4) index(a,IDX_COMMBASUBSHIST_1) index(b,IDX_COMMCMSERVHIST_1)*/
    1,
    t.DISC_ID,
    t.DISC_LEV,
    to_date(20140117082042, &#39;yyyymmddhh24miss&#39;),
    t.MSINFO_ID,
    t.ORG_ID,
    t.SERV_ID,
    t.SUBS_ID,
    t.OBJ_GRP_ID,
    a.SUBS_CODE,
    a.SUBS_STAT,
    a.SUBS_STAT_REASON,
    a.SUBS_STAT_DATE,
    a.ACTION_ID,
    a.ACTION_TYPE,
    a.ACTION_EX_TYPE,
    a.ACT_DATE,
    a.REQ_ID,
    a.STAFF_ID,
    a.CMMS_CUST_CODE,
    a.SPEED_VALUE,
    b.ACC_NBR,
    b.CUST_ID,
    b.SERV_NBR,
    b.CONSUME_GRADE,
    b.SERV_LEV,
    b.ACCOUNT_NBR,
    b.CITY_VILLAGE_ID,
    b.SERV_CHANNEL_ID,
    b.SERV_STAT_ID,
    b.CUST_CLASS_DL,
    b.CUST_TYPE_ID,
    b.USER_TYPE,
    b.USER_CHAR,
    b.PAYMENT_TYPE,
    b.BILLING_TYPE,
    b.PROD_ID,
    b.PROD_CAT_ID,
    b.EXCHANGE_ID,
    b.SERV_COL1,
    b.SERV_COL2,
    b.AREA_ID,
    b.SUBST_ID,
    b.BRANCH_ID,
    b.STOP_TYPE,
    b.CUST_MANAGER_ID,
    b.CREATE_DATE,
    b.ADDRESS_ID,
    b.SUBS_DATE,
    b.OPEN_DATE,
    b.MODI_STAFF_ID,
    b.CMMS_CUST_ID,
    b.CUST_NAME,
    b.SALES_ID,
    b.SALES_TYPE_ID,
    b.SERV_ADDR_ID,
    t.HIST_CREATE_DATE,
    b.ARREAR_MONTH,
    b.ARREAR_MONTH_LAST,
    t.SALESTAFF_ID,
    t.EHOME_TYPE,
    t.EHOME_CLASS,
    b.strat_grp_dl,
    b.sale_org1,
    b.sale_org2,
    b.sale_org3,
    b.location_type,
    b.region_flag,
    b.terminal_id,
    b.pstn_id,
    b.fee_id,
    b.payment_id,
    b.billing_id,
    b.strat_grp_xl,
    b.fld1,
    b.fld3,
    b.cust_level,
    b.group_cust_type,
    b.cust_region,
    b.group_cust_grade,
    b.control_level,
    b.net_connect_type,
    b.trade_type_id,
    b.acc_nbr2,
    b.cdma_class_id,
    b.phone_number_id,
    b.develop_channel,
    b.online_time,
    t.wireless_type,
    b.new_serv_stat_id,
    b.is_phs_tk,
    b.serv_grp_type,
    b.state,
    t.cdma_disc_type,
    b.mix_disc,
    b.is_3g,
    t.add_disc_type,
    to_number(nvl(b.business_type, &#39;-1&#39;)),
    nvl(t.label_num, -1),
    b.is_mix_prod,
    t.price_id,
    t.disc_item_id,
    b.STD_SUBST_ID,
    b.STD_BRANCH_ID,
    t.DISC_ITEM_ID_OP,
    t.PRICE_ID_OP,
    t.business_type,
    b.new_prod_id,
    b.BOARD_SUBST_ID,
    b.BOARD_BRANCH_ID
     from RPT_COMM_BA_SUBS_HIST  a,
          RPT_COMM_CM_SERV_HIST  b,
          TB_COMM_BA_MSDISC_TEMP t
    where a.subs_id = t.subs_id
      and b.serv_id = t.serv_id



--同事说开销比较大。有450W。。下面是执行计划：
<img src="/static/imghw/default1.png"  data-src="http://img.blog.csdn.net/20141025102001913?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZ2RtemxoajE=/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/Center"  class="lazy" alt="" />
 
/*
涉及的表大小：
OWNER	SEGMENT_NAME	SEGMENT_TYPE	Size(Mb)
SUMMARY_SJZ_GZ	TB_COMM_BA_MSDISC_TEMP	TABLE	40
SUMMARY_SJZ_GZ	RPT_COMM_CM_SERV_HIST	TABLE PARTITION	9016.1875
SUMMARY_SJZ_GZ	RPT_COMM_BA_SUBS_HIST	TABLE PARTITION	67330.25

以下是优化思路：
强制使用索引，导致其中9g的表走了index full scan，然后回表。因为除了index fast scan以外，其他索引扫描都是单块读，回表又是单块读。导致速度非常慢。优化时考虑使用哈希连接，40Mb的小表作为驱动表，连接9g的表，最后连接超大的67G的表。
优化时使用的技术：
1.	use_hash（a，b），使用哈希表关联方式
2.	/*+parallel(a 5)*/;并行处理
3.	db_file_multiblock_read_count多块读参数设置为最大
4.	workarea_size_policy设置为手工管理
5.	sort_area_size设为接近最大
6.        hash_area_size设为接近最大

<p>5小时不出结果，优化后20分钟不到出结果，就是这么神奇。</p><p>alter session enable parallel dml;
alter session set workarea_size_policy=manual;
alter session set sort_area_size=2100000000;
alter session set hash_area_size=2100000000;
alter session set db_file_multiblock_read_count=128;




select &#160;/*+parallel(a,5) parallel(b,5) parallel(t,5) leading(t) use_hash(t,b) user_hash(b,a)*/
&#160; &#160; &#160;1,
&#160; &#160; t.DISC_ID,
&#160; &#160; t.DISC_LEV,
&#160; &#160; to_date(20140117082042, &#39;yyyymmddhh24miss&#39;),
&#160; &#160; t.MSINFO_ID,
&#160; &#160; t.ORG_ID,
&#160; &#160; t.SERV_ID,
&#160; &#160; t.SUBS_ID,
&#160; &#160; t.OBJ_GRP_ID,
&#160; &#160; a.SUBS_CODE,
&#160; &#160; a.SUBS_STAT,
&#160; &#160; a.SUBS_STAT_REASON,
&#160; &#160; a.SUBS_STAT_DATE,
&#160; &#160; a.ACTION_ID,
&#160; &#160; a.ACTION_TYPE,
&#160; &#160; a.ACTION_EX_TYPE,
&#160; &#160; a.ACT_DATE,
&#160; &#160; a.REQ_ID,
&#160; &#160; a.STAFF_ID,
&#160; &#160; a.CMMS_CUST_CODE,
&#160; &#160; a.SPEED_VALUE,
&#160; &#160; b.ACC_NBR,
&#160; &#160; b.CUST_ID,
&#160; &#160; b.SERV_NBR,
&#160; &#160; b.CONSUME_GRADE,
&#160; &#160; b.SERV_LEV,
&#160; &#160; b.ACCOUNT_NBR,
&#160; &#160; b.CITY_VILLAGE_ID,
&#160; &#160; b.SERV_CHANNEL_ID,
&#160; &#160; b.SERV_STAT_ID,
&#160; &#160; b.CUST_CLASS_DL,
&#160; &#160; b.CUST_TYPE_ID,
&#160; &#160; b.USER_TYPE,
&#160; &#160; b.USER_CHAR,
&#160; &#160; b.PAYMENT_TYPE,
&#160; &#160; b.BILLING_TYPE,
&#160; &#160; b.PROD_ID,
&#160; &#160; b.PROD_CAT_ID,
&#160; &#160; b.EXCHANGE_ID,
&#160; &#160; b.SERV_COL1,
&#160; &#160; b.SERV_COL2,
&#160; &#160; b.AREA_ID,
&#160; &#160; b.SUBST_ID,
&#160; &#160; b.BRANCH_ID,
&#160; &#160; b.STOP_TYPE,
&#160; &#160; b.CUST_MANAGER_ID,
&#160; &#160; b.CREATE_DATE,
&#160; &#160; b.ADDRESS_ID,
&#160; &#160; b.SUBS_DATE,
&#160; &#160; b.OPEN_DATE,
&#160; &#160; b.MODI_STAFF_ID,
&#160; &#160; b.CMMS_CUST_ID,
&#160; &#160; b.CUST_NAME,
&#160; &#160; b.SALES_ID,
&#160; &#160; b.SALES_TYPE_ID,
&#160; &#160; b.SERV_ADDR_ID,
&#160; &#160; t.HIST_CREATE_DATE,
&#160; &#160; b.ARREAR_MONTH,
&#160; &#160; b.ARREAR_MONTH_LAST,
&#160; &#160; t.SALESTAFF_ID,
&#160; &#160; t.EHOME_TYPE,
&#160; &#160; t.EHOME_CLASS,
&#160; &#160; b.strat_grp_dl,
&#160; &#160; b.sale_org1,
&#160; &#160; b.sale_org2,
&#160; &#160; b.sale_org3,
&#160; &#160; b.location_type,
&#160; &#160; b.region_flag,
&#160; &#160; b.terminal_id,
&#160; &#160; b.pstn_id,
&#160; &#160; b.fee_id,
&#160; &#160; b.payment_id,
&#160; &#160; b.billing_id,
&#160; &#160; b.strat_grp_xl,
&#160; &#160; b.fld1,
&#160; &#160; b.fld3,
&#160; &#160; b.cust_level,
&#160; &#160; b.group_cust_type,
&#160; &#160; b.cust_region,
&#160; &#160; b.group_cust_grade,
&#160; &#160; b.control_level,
&#160; &#160; b.net_connect_type,
&#160; &#160; b.trade_type_id,
&#160; &#160; b.acc_nbr2,
&#160; &#160; b.cdma_class_id,
&#160; &#160; b.phone_number_id,
&#160; &#160; b.develop_channel,
&#160; &#160; b.online_time,
&#160; &#160; t.wireless_type,
&#160; &#160; b.new_serv_stat_id,
&#160; &#160; b.is_phs_tk,
&#160; &#160; b.serv_grp_type,
&#160; &#160; b.state,
&#160; &#160; t.cdma_disc_type,
&#160; &#160; b.mix_disc,
&#160; &#160; b.is_3g,
&#160; &#160; t.add_disc_type,
&#160; &#160; to_number(nvl(b.business_type, &#39;-1&#39;)),
&#160; &#160; nvl(t.label_num, -1),
&#160; &#160; b.is_mix_prod,
&#160; &#160; t.price_id,
&#160; &#160; t.disc_item_id,
&#160; &#160; b.STD_SUBST_ID,
&#160; &#160; b.STD_BRANCH_ID,
&#160; &#160; t.DISC_ITEM_ID_OP,
&#160; &#160; t.PRICE_ID_OP,
&#160; &#160; t.business_type,
&#160; &#160; b.new_prod_id,
&#160; &#160; b.BOARD_SUBST_ID,
&#160; &#160; b.BOARD_BRANCH_ID
&#160; &#160; &#160;from SUMMARY_SJZ_GZ.RPT_COMM_BA_SUBS_HIST &#160;a,
&#160; &#160; &#160; &#160; &#160; SUMMARY_SJZ_GZ.RPT_COMM_CM_SERV_HIST &#160;b,
&#160; &#160; &#160; &#160; &#160; SUMMARY_SJZ_GZ.TB_COMM_BA_MSDISC_TEMP t
&#160; &#160; where a.subs_id = t.subs_id
&#160; &#160; &#160; and b.serv_id = t.serv_id
</p>

로그인 후 복사

본 웹사이트의 성명

본 글의 내용은 네티즌들의 자발적인 기여로 작성되었으며, 저작권은 원저작자에게 있습니다. 본 사이트는 이에 상응하는 법적 책임을 지지 않습니다. 표절이나 침해가 의심되는 콘텐츠를 발견한 경우 admin@php.cn으로 문의하세요.