Hi Neil, As Krishna said, Innodb is generally always superior to MyISAM unless you need full-text search (and even if you do there are alternatives to MyISAMs full-text search, which I've often found to be lacking in performance).
A poorly optimised query will be slow whether it is called from a procedure or executed directly by the page. I'd advise analysing your joined queries carefully, using the EXPLAIN tool in MySQL, and add appropriate indexes to your tables. Also, if you are developing in PHP, you may wish to look at the memcache module, which can cache function results in memory in PHP. This can often be helpful for storing results for very frequently called queries. On Thu, 2010-03-18 at 09:18 +0000, Tompkins Neil wrote: > Hi > > I'm currently looking to develop an on line web application - which is going > to be used by around 200+ concurrent users at any one time. Can > you recommend to me the best/preferred MySQL database engine to use for > example MyISAM ? > > Also, in your experiences, do you recommend that SELECT statements > containing a number of INNER JOINS should be execute from a Stored procedure > or purely from the webpage ? > > Cheers > Neil -- Ian Simpson System Administrator MyJobGroup -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
