On Thu, 2001-12-13 at 03:54, Robert Sundström wrote:
> queries, with medium sized transactions (3-5 statements per transaction,
> where transactions was supported). On my regular desktop box I was able to
> get about 700 statements per second using MyISAM and about two thirds of
> that using InnoDB. Already at 2 simultaneous users (doing the same
> transactions) total throughput was less than for the single user case.
Look and see what your innodb_buffer_pool_size setting is. The thing I
keep running into when helping people make use of Innodb is that they
either don't understand it or they think it is similair to the
record_buffer setting (which is just wrong).
If you are from an Oracle world think of it as your SGA. If you tune
it as you tune your SGA you will see a dramatic increase in performance.
One of the great things about MySQL is it installs so easily. If you
have ever been through an Oracle install (or hell DB2) you realize
how much easier it is to install MySQL.
Problem is, the default install is probably not going to be very tuned
for your environment most likely.
> Most stable commercial products exposes the opposite behavior. It may be
> the case that MySQL performs pretty well in single (or few) user cases, but
> the commercial alternatives will, in my experience, in most cases beat
> MySQL on 3-5 users and above.
I have worked in a shop where we replaced MySQL with Oracle. What was
running at the time on a 6 processor ALR box needed 3 Sun 4500's to
run nearly as well. This was also 3 years ago.
Today there wouldn't have been the need to do conversion.
> It is also the case that most commercial products supports better
> optimization methods than MySQL. Two important things are caching statement
> compilations at the server and stored procedures. If I have a performance
Stored procedures just add more load to your database. Assuming you are
in a production environment where you are paying for each processor your
database has, stored procedures are very costly compared to just adding
a farm of frontend servers to do the labor. The one instance where this
can make a lot of difference is if moving the data is highly expensive.
In that case if you don't want to shover several gigs of data across
your pipe a stored procedure works quite well.
The two cases where I currently need to keep from doing this I just
use myperl() in MySQL and let it do the work (and even if you hate perl
you have to admit it is a lot prettier then PL/SQL).
-Brian
--
_______________________________________________________
Brian Aker, [EMAIL PROTECTED]
Slashdot Senior Developer
Seattle, Washington
http://tangent.org/~brian/
Email/Jabber [EMAIL PROTECTED]
_______________________________________________________
You can't grep a dead tree.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
