MySQL record limit...

[Anon]

i'm getting ready to deploy a large scale corporate intranet site which runs on solaris, php, apache and mysql.

how stable is mysql using the standard tables myisam tables with 100,000 records in a given table? 500,000? 1,000,000? 10,000,000?

how many records would i have to require before i should really consider switching to oracle?

thanks!

[Anon]

The speed of your database will depend on the complexity of your queries. I have benchmarked MySQL to be faster than Oracle for simple queries but it lagged way behind when using complex queries. # of records=1,000,000+

However, you of course know that a complex query can be written down via a series of simple queries. So, it really is your choice.

[Anon]

thanks... i had just read somewhere that mysql starts to choke around 100,000 records, and that frightened me...

my queries are ALL VERY simple...

select from blah...
update blah...

never joining tables or anything complicated... so i should be ok for a long time.

[Anon]

I have a database that has a table using nearly 500,000 records in it right now. It is still working fairly stable.

However, if you had no indexes set up, I could very well see how mysql could start to choke up at 100,000 records. As with any database, indexes are vital to mysql's performance.

[Anon]

i didn't mean in general, i meant in this forum application that would do MANY recursive queries and updates to the same table on the same page.

lets say you get 5,000,000 page views a day to the forum: you probably have to get everying done in under 2 seconds to keep the server alive. with recursive queries to a table that is actively getting updated, and current data is crucial, then it would probably start zonking out earlier than 500,000 records.

i have a small mysql table with something like 10 million records and everything still works fine... it is almost solely selected from though, and everything is very well indexed