SQL/Python question -- slow... What is the fixed cost?

[Mark Berry]

On Thu, 04 Oct 2001 11:30:17 -0500, Leonardo B Lopes
<leo at iems.nwu.edu> wrote:

>Thanks Mark! Actually I am doing my best to keep my system independent
>of mysql. And my db is quite particular: It is only written to once.
>After that, it is only queried, and even so in a quite particular way.
>But my db is pretty big. This instance, for example, has a table with
>83000+ records. It is not so much that the query joining that table with
>2 others takes .001 cpusec that worries me. That is OK. The problem is
>that some other pretty simple queries also take the same time. If that
>is always the case, then I will have to find another quite more
>sophisticated solution for data storage, and that is what I am trying to
>avoid.


My advice on this, MySQL will act completely differently when there
are 20-30 concurrent connections than 1-2.  They don't seem to have
the sofistication in locking to handle heavy loads.  Some very high
volume websites strugle to get around this problem (slashdot).  If you
are not doing anything highly concurrent, then you shouldn't have any
problem at all with MySQL.  

good luck :)

>
>Cheers,
>Leo. 
>