Re: Re: massive MySQL tables

One other point to make is the shear speed of MySQL. I believe you should be focusing more on useabilty currently than peak performance. MySQL will handle a lot of crap - and do it fast. I love this mailing list. -Jason Garber IonZoft.com At 10:28 AM 10/10/2001 +0800, Sanbao Lin wrote:

Hi all, Thanks for the comments / help. I've decided to "walk before running", starting with the most simple solution possible (85 fields per row, single page form) to do some testing. If it works out, i'm happy, if not I know I have invest some more time/money. In discussion with the client, we determined that the application itself will NOT get many hits -- they can imagine a MAXIMUM of 30 applications per week, so we're really talking about 2 hits per hour, not 2 per minute. I've also made a point of NOT indexing many fields, since this will cause a performance hit on writing / modifying, and we'll establish WHICH fields need indexing over the coming months. So, as long as the HTML renders fast enough, I think i'm okay for the monent :) But some testing will tell the full story in the coming weeks! Justin -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net