锘??xml version="1.0" encoding="utf-8" standalone="yes"?>
1.1鏂囦歡澶у皬
鍦ㄩ渶瑕佷嬌鐢ㄨ繖涓〉闈㈡椂鐢ㄦ埛闇瑕佸姞杞藉灝戞暟鎹傘?BR> 60-100K 欏甸潰澶у皬 淇濇寔鏁欏皬鐨勬枃浠?BR> 1.2鍙嶅簲鏃墮棿
浣犲悜鏈嶅姟鍣ㄥ彂閫佽姹傚拰鏁版嵁鍒拌揪PC鐨勬椂闂撮棿闅?BR> 緗戠粶鍙嶅簲鏃墮棿
2.鍑忓皯鏂囦歡澶у皬
100K浠ヤ笂
澶ч噺鐨勬枃浠跺綋鍓嶄富瑕佹槸鐢卞法澶х殑Javascript綾誨簱銆?BR> 宸ㄥぇ鐨勫浘鐗?BR> 鑰佺殑HTML鏍峰紡涔熶細浜х敓澶ф枃浠訛紝灝藉彲鑳藉湴浣跨敤XHTML鍜孋SS
鍘嬬緝
3.鏌ユ壘浠涔堝鑷翠簡寰堥珮鐨勫弽搴?BR> 濡備笂鎴戜滑鎵鎻愬埌鐨勶紝鍙嶅簲鏃墮棿涓昏鐢變袱涓富瑕佺殑鍏冪礌
3.1緗戠粶鍙嶅簲鏃墮棿
3.2鏄惁鑺辮垂浜嗗お闀跨殑鏃墮棿鏉ヤ駭鐢熼〉闈?BR> 3.3鎬ц兘
4.紜畾緇濈紭緇勪歡
5.緙栬瘧緙撳瓨
6.鏌ョ湅DB鏌ヨ
閬垮厤join. 鏌ヨ緙撳瓨
7.鍙戦佹紜殑宸蹭慨鏀規暟鎹?BR>8.鑰冭檻緇勪歡緙撳瓨
9.鍑忓皯鏈嶅姟鍔犺澆
9.1浣跨敤鐩稿弽鐨勪唬鐞?BR> 9.2閲囩敤杞婚噺綰х殑HTTP鏈嶅姟鍣?BR>10. 澧炲姞鏈嶅姟鍣?BR>
This is a quickly hacked tool to do statistics錛堢粺璁★級 on SELECT queries in order to know where it is most efficient to create indexes. 鐩殑鏄渶鏈夋晥鐨勫垱寤虹儲寮?
This small tool, released under an Apache-based license connects to the P6Spy JDBC logger and displays in real time the queries going to the database. It uses an integrated SQL parser to build statistics on the most accessed tables and columns and can generate SQL index creation files. Other information is also gathered and displayed, such as the request time for a single request, for a class of request, and for all the requests. Sorting may be done on these views to detect(瀵熻) database problems efficiently.
This tool can be very useful when you have a big volume of queries that you need to analyze not one by one涓涓帴涓涓?(meaning that the specific time isn't that much of interest), but rather(鑻ラ潪) when you want to know what "group" of queries is taking a lot of time, such as queries on the same tables and columns but with different query values. The integrated SQL parser (built with ANTLR) is used to analyze the incoming SELECT queries.
The Swing GUI was based on Apache's Log4J Chainsaw, but all the bugs are mine. Also contributors are welcome to test, make new suggestions, give their opinion and submit patches.