This is good information.
What I love to see is the correlation between how much goes out to the user vs. how much the server needs.
Why is there a need for the DB server to ship 40Mbits to the Web server, when the Web server only serves up, at most 4Mbits? Clearly a lot of the data is discared.
This is where stored routines on the DB server would come very handy. Instead of requesting a record, manipulating, then requesting an other record, manipulating... etc. 4,000 times - it could be shifted to the DB server.
Anyone experiment with rewriting some of the more DB intensive routines as stored routine?
|