wuqiSpank's unique "SQL Sequence Diagram" and live SQL performance graphs make it possible.
Who is responsible for software performance? The developers who coded the system or a performance tuning team? It time to finally draw the line of responsbilities of who owns what. With wuqiSpank, we finally have a tool that helps developers understand and take responsibility for the performance of their code's SQL data access strategy.
- Like no other tool in the industry, wuqiSpank's unique "table centric" SQL sequence diagrams show the well-known SQL anti-patterns that heavily impact performance.
- How does wuqiSpank get your SQL? Manual import (all platforms) or live SQL tracing (Java only).
- For Java applications, wuqiSpank shows the exact line of Java code that executed SQL statement.
- Will performance suffer when moving from a small dev database to a large prod db? Here is wuqiSpank's plan to help avoid that.
- wuqiSpank groups together all SQL from single click of your web app (Java only).
A wuqi is an Unnecessary Query Invocation. But but but what does the W stand for? Woefully. wuqiSpank spanks wuqis. Got it?more efficiently with this single query:
SELECT * FROM CUSTOMER C, ACCOUNT A WHERE C.CUST_ID = A.CUST_ID AND C.CUST_ID IN (SELECT CUST_REL_ID FROM CUST_CUST_REL WHERE CUST_ID = 'SPANK-001')
Use EHCache or similar to avoid the performance overhead of querrying for static data you've already retrieved. The graph below shows SELECT statements pulling data from two tables whose contents change so rarely, their data should be cached at system startup. Wuqispank prominently displays the table names (PHYSICAL_PLANT and PRODUCT) near the circles at the time of the graph, so you can quickly determine whether the activity is appropriate for the give tables.
Wuqispank shows the exact line number that a SQL statement was executed from. The blue rectangle acts like the MS-Excel cursor and the large window at the bottom displays the detail you can't see in a single table cell.
Wuqispank highlights repetetive sequences of the same SQL statements. These are ripe for optimization! (NOTE: wuqiSpank doesn't know how to use a yellow highlighter -- there's that whole issue of opposable thumbs).