Krishna Chandra Prajapati wrote:
Hi shawn,
As the data grows to 20 millions the insert rate will become very slow.
In such case i am getting 2000 insert/seconds only.
Therefore my objective is not achieved.
I cannot slow up the insert rate of 10,000/second. I am getting data
(inserted by us
If you only need very fast INSERTs, you might try to use ARCHIVE
storage engine (
http://dev.mysql.com/tech-resources/articles/storage-engine.html ). It
was developed for handling INSERTs very fast. Many peoples use it, for
example, for storing logs.
> Hi list,
>
> I want to insert 1 records/s
non-linearity in the insert rate means you have indexes on some columns.
depending on your situation, mysql can be more efficient if drop those
indexes, do bulk inserts, and then add the indexes again.
On 1/23/10 5:02 AM, "Krishna Chandra Prajapati"
wrote:
> Hi shawn,
>
> As the data grows to
Hi shawn,
As the data grows to 20 millions the insert rate will become very slow. In
such case i am getting 2000 insert/seconds only.
Therefore my objective is not achieved.
I cannot slow up the insert rate of 10,000/second. I am getting data
(inserted by users at this rate)
Is there any other
Krishna Chandra Prajapati schrieb:
> Hi list,
>
> I want to insert 1 records/sec into table. There can be n number of
> tables with unique data in each. What are the possible ways to do ?
>
i prefer mysqlimport. just sort your output into a file that is named like the
table
you wish to i
Krishna Chandra Prajapati wrote:
Hi list,
I want to insert 1 records/sec into table. There can be n number of
tables with unique data in each. What are the possible ways to do ?
Thanks,
Krishna
The manual is your friend. It doesn't hurt to consult it.
INSERT ...
http://dev.mysql.com/doc
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,
On Tue, Apr 1, 2008 at 5:39 PM, Michael Katz <[EMAIL PROTECTED]> wrote:
> In a replication environment with 1 master and a 2 slaves, does the
> entire database always have to be stored on the master? I understand
> that slaves can come on and off line but I am not sure if the master
> must
awesome yes I will be an eager consumer.
-C
- Original Message -
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "chad pratt" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 23, 2003 9:01 PM
Subject: Re: scaling
> On Mon, Jun
On Mon, Jun 30, 2003 at 11:44:30PM -0400, chad pratt wrote:
> thanks for the invite. I am too poor to attend.
The slides will all be on-line within a day of the talk, if that's of
any help.
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
<[EMAIL PROTECTED]> | http://jeremy
thanks for the invite. I am too poor to attend.
-C
- Original Message -
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "chad pratt" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 23, 2003 6:58 PM
Subject: Re: scaling
> On Sa
On Sat, Jun 28, 2003 at 10:53:48PM -0400, chad pratt wrote:
>
> What are the gotchas with respect to scaling?
Come to OSCON and find out!
http://conferences.oreillynet.com/cs/os2003/view/e_sess/4502
Sorry. They ask that speakers promote their talks on a relevant
mailling list if they get a c
On Fri, Nov 02, 2001 at 03:37:53PM -0800, another oracle dba wrote:
> Hi.
>
> I have a query which completes in about 9 sec when executed alone,
> but the time grows dramatically when I execute several similar
> queries at the same time. If I execute 3 queries the time grows to
> 27-40sec, for 5
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
Have you considered replication? There's a pretty good chapter in the MySQL
manual on how to objectively determine the benefit to a master/slave setup
with n slaves (it depends on how often writes happen to the database).
- Original Message -
From: "vinod panicker" <[EMAIL PROTECTED]>
To
23 matches
Mail list logo
