No disagreement with any of your observations about the PC platform, but I'm
stuck there for the time being. Is there some good doc on optimizing MySQL
that you could recommend? My DB is around 10K records and around 15-20
tables, so not too huge, yet. When the server isn't loaded, my app is really
zippy. But get a few too many people running the app and performance falls
off a cliff. Is there somewhere that I can specify how many simultaneous
queries can be run? Also, does the DB get locked only on updating or
inserting, but not selecting? That is my expectation.

--
Richard Gordon
YAKiToMe! Co.
Lead YAK
"Michael Austin" <maustin@firstdbasource.com> wrote in message
news:sfNRj.3129$1b7.1204@newssvr13.news.prodigy.ne t...
> weheh wrote:
>> I have a mysql-based dynamic web app that's slowing down at an
>> unacceptable rate as my numbers of users climbs. Can anyone help me
>> figure out how to tune the database so that it runs faster? I've looked
>> at the my.ini file (I'm on windows server) and beefed up most of the
>> numbers, but don't see any change after rebooting my server. I'm
>> relatively experienced at creating mysql DBs, but a relative newbie when
>> it comes to administering mysql -- so I don't really know where to start.
>> I have already tuned the application to minimize the number of calls to
>> the database, so that base is covered. Thanks for helping out.
>
>
> You are on a windows box and you wonder why your app slows down when you
> add too many users?
>
> Your next step is to run explain plans for the most called sql statements
> to ensure you have them indexed properly. If you have a few users doing
> full table scans - that may not be too bad - but increase that and
> depending on the size of the query, you can bring down a peecee pretty
> easily. I once was called to help fix a problem where a web page
> submitted 5 full table scans returning over 400Mb for each query to a
> mainframe database. It crippled the mainframe and took more than 8 hrs for
> it to recover.
>
> After doing this - move the database to a server that can handle it. Just
> because it can run on a platform, doesn't mean that it should. And ALL of
> the Windows OS's are bloated and perform very poorly regardless of OS
> tuning.
>