Hello,
I would like to hire a seasoned MySQL DBA for a short consulting job. I need
to migrate a website with a peak traffic of ~3k pageviews / second from an
Oracle database running on big iron to a MySQL set up. The 3k is of course a
ballpark figure, and we cache content aggressively but as the
Friday, August 21, 2009 9:23 PM
> To: wha...@bfs.de
> Cc: MySQL
> Subject: Re: Scaling Mysql
>
> Hi wharms,
>
> Yor are right. It's some kind of queue mechanism. Right now i am working i
> telco company (We used to send sms)
>
> Users will be inserting recor
Have you looked at MySQL cluster? It was created specifically for telco needs.
-Original Message-
From: Krishna Chandra Prajapati [mailto:prajapat...@gmail.com]
Sent: Friday, August 21, 2009 9:23 PM
To: wha...@bfs.de
Cc: MySQL
Subject: Re: Scaling Mysql
Hi wharms,
Yor are right. It&#
Hi wharms,
Yor are right. It's some kind of queue mechanism. Right now i am working i
telco company (We used to send sms)
Users will be inserting records into send_sms @ 30,000msg/min Then those
record will be updated and moved to alt_send_sms and deleted from send_sms.
After that 30,000msg/min
I forgot. It's all done in one sql statement.
Mike
-Original Message-
From: Jerry Schwartz [mailto:jschwa...@the-infoshop.com]
Sent: Friday, August 21, 2009 8:32 AM
To: 'mos'; 'MySQL'
Subject: RE: Scaling Mysql
>
>Krishna,
> Rather than copying
>-Original Message-
>From: Gavin Towey [mailto:gto...@ffn.com]
>Sent: Friday, August 21, 2009 2:45 PM
>To: Jerry Schwartz; 'mos'; 'MySQL'
>Subject: RE: Scaling Mysql
>
>RENAME statement is atomic, and you can specify multiple tables to rename
a
hwa...@the-infoshop.com]
Sent: Friday, August 21, 2009 8:32 AM
To: 'mos'; 'MySQL'
Subject: RE: Scaling Mysql
>
>Krishna,
> Rather than copying rows from one table to another, and deleting the
>previous rows, why not just do:
>
>1) create table send_sms_emp
>
>Krishna,
> Rather than copying rows from one table to another, and deleting the
>previous rows, why not just do:
>
>1) create table send_sms_empty like send_sms;
>
>2) rename table send_sms to send_sms_full;rename send_sms_empty to
send_sms;
>
>3) insert into alt_send_sms select * from send_
At 01:30 AM 8/21/2009, Krishna Chandra Prajapati wrote:
Hi list,
I have two tables send_sms and alt_send_sms. Users are inserting records
into send_sms @ 500/sec ie 3/min. After applying some updates to
send_sms data are transferred to alt_send_sms and deleted from send sms. The
same thing i
Krishna Chandra Prajapati schrieb:
> Hi list,
>
> I have two tables send_sms and alt_send_sms. Users are inserting records
> into send_sms @ 500/sec ie 3/min. After applying some updates to
> send_sms data are transferred to alt_send_sms and deleted from send sms. The
> same thing is happeni
Hi list,
I have two tables send_sms and alt_send_sms. Users are inserting records
into send_sms @ 500/sec ie 3/min. After applying some updates to
send_sms data are transferred to alt_send_sms and deleted from send sms. The
same thing is happening with alt_send_sms table.
Is it possible to in
My application is intended to be scalable. In the eyes of the marketing
departments, it should be scalable from zero to infinity. But we all know
that this is not possible indefinitely - at some point you reach a
bottleneck. In the case of my system, that bottleneck will eventually be
the MySQL wri
r" <[EMAIL PROTECTED]>
From:"Jason Landry" <[EMAIL PROTECTED]>
Date:Sat, 3 Mar 2001 03:38:10 -0600
CC:<[EMAIL PROTECTED]>
Subject: Re: Scaling mysql
Have you considered replication? There's a pretty good chapter in the MySQL
manual on how to objectively determine
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 02, 2001 1:24 PM
Subject: Scaling mysql
> hey,
> i'm having a problem with scaling a mysql server. This is the
situation... i have a database with 5 tables containing user data.
hey,
i'm having a problem with scaling a mysql server. This is the situation... i have
a database with 5 tables containing user data. Except one, all the other tables have
only 2 fields. This data is queried often and needs to be accessed by multiple web
servers. Each table would contai
15 matches
Mail list logo
