I hate to burst your bubble, but 367,000 updates in 24 hours translates to an average of 4.5 trasactions per secon... If you assume those updates only occur within an 8 our window that's still a little under 13 transactions per second. Any decent server (HW) wise should be able to handle that load without too much trouble. However, if I'm not mistaken, the database at livejournal doesn't get hit nearly as much because of the memcached (at least for queries).

Paul

Russell Horn wrote:
It is better to stay with Postgres. If you don't want to loose your
business stay away from MySQL.


Oh come on, there are many reasons to use Postgres, but this is just FUD.

Just as an example off the top of my head, take a look at
http://www.livejournal.com/stats.bml (2.5 million active accounts,
367,000 updates in the last 24 hours and all on a mysql backend).

There's a host of other big sites all using MySQL - Yahoo! Finance,
Slashdot (handling 360 queries per second) and others.  If you're
losing data on MySQL with 10 users you have a configuration or coding
problem.

Again, Postgres offers many features that MySQL does not and vice
versa, but to suggest that MySQL shouldn't be used because you'll
loose data is a bogus argument.

Russell.
_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


_______________________________________________
Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to