Geoffrey,

1. There shouldn't be any MyISAM tables at all (aside from maybe the information schema), that's a problem right there.
2. Hopefully you're on Windows Server 2012?
3. It seems like you should still be able to move onto MySQL 5.6 which has InnoDB improvements.
4. 'SELECT *' should be rare in code.  It would be better if the developers were using an ORM and weren't writing very much SQL but that's probably not under your purview.
5. If you can find the top 5 queries by time, do an 'explain' on each one and you'll see whether indexes will help.  Be careful because indexes can slow down INSERTs and UPDATEs.
6. You might be able to reduce what gets logged - although that's a minor improvement usually.
7. MySQL works better under Linux.  I know that's a big change but it's worth thinking about over the longer term.

-Adam


--
Kili - Cloud for Africa: kili.io
More Musings: varud.com

On Mon, Nov 17, 2014 at 2:08 PM, geoffrey gitagia <ggitagia@gmail.com> wrote:

Thanks Adam
    I am running on a windows environment so I have 5.5 on it , I noticed is writes alot of temp files and at times converts to isam tables ,meaning that my io is going to be high ,from me resource monitor I can see lots of disk activities, it even at times freezes the server for a few seconds, another problem is that the tables have many columns of which the dev uses select * statements,  impacting on cache.