Joshua Chamas writes:
> sinisa@stripped wrote:
> >
> > Anyway, optimizing a schema should be constricted to normalization
> > processes only , and not to locking, which in itself does not prosent
> > much problems. I must consent that I do not understand a need to have
> > million of tables !
> >
>
> Its a high OLTP application, with roughly 5,000,000+ inserts
> a week mixed with user driven selects on those same rows.
> I need to find the best way to break it up so there aren't
> too many collisions.
>
> Thanks for your help Sinisa!
>
> -- Joshua
> ______________________________________________________________________
> Joshua Chamas Chamas Enterprises Inc.
> NODEWORKS - web link monitoring Long Beach, CA USA 1-562-432-2469
> http://www.nodeworks.com http://www.chamas.com
>
Hi!
Thanks for nothing !!
There are customers with 1.000.000 inserts per day.
They usually make temp working tables, on per day basis.
MySQL is very efficient and can handle huge tables, particularly with
3.23.2 adn MYISAM tables.
It would be easier to you to have an archive and an working table for
each entity, instead of dissipating so much and getting involved in
possibly difficult table management problems.
Sinisa
+----------------------------------------------------------------------+
| TcX ____ __ _____ _____ ___ == mysql@stripped |
| /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic |
| /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sinisa@stripped|
| /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaka, Cyprus |
| /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ |
| ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ |
| /*/ \*\ Developers Team |
+----------------------------------------------------------------------+
