On Montag 14 September 2009 Jonathan Feally wrote:
innodb_flush_log_at_trx_commit=2
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
//
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
S
___
DBmail mailing list
Simon Gray wrote:
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
If you have minimal writes and the server is on a
Jonathan Feally wrote:
Simon Gray wrote:
Michael Monnerie wrote:
Note:
Everybody who care about their data, you should leave this setting on
it's default 1:
innodb_flush_log_at_trx_commit=1
Also, this will only affect writes - rather than reads.
If you
On Dienstag 15 September 2009 Jonathan Feally wrote:
If you have minimal writes and the server is on a UPS, this setting
won't make too much difference
I have a home server on UPS, and can tell you from real experience what
crashes I hade despite all this:
1) Broken power supply - UPS doesn't
How much data are you searching through? (how big is your dbmail db?)
Roughly 100 GB; it's got 750K messages or so.
How much ram does the db server have?
2 GB
How much ram is allocated to the db software?
How do I check?
Are you running MySQL or Postgres? or something else?
MySQL
If
Hey, all. I've got a bajillion e-mails in my e-mail. (I'm using dbmail
for archiving.) I don't care about disk space -- I've got it to throw
away. But searches take close to 5+ minutes. Any clues on indexing,
etc., that might be appropriate?
-Ken
--
This message has been scanned for
Ken D'Ambrosio wrote:
Hey, all. I've got a bajillion e-mails in my e-mail. (I'm using dbmail
for archiving.) I don't care about disk space -- I've got it to throw
away. But searches take close to 5+ minutes. Any clues on indexing,
etc., that might be appropriate?
-Ken
How much
Ken D'Ambrosio wrote:
How much data are you searching through? (how big is your dbmail db?)
Roughly 100 GB; it's got 750K messages or so.
You need to clean and optimize your tables. With a quick calc, that
would put you at about 140MB/message. Are you on 2.2.x or 2.3.x?
You should
Thanks for all the pointers! Though I'm afraid your sliderule* dropped a
decimal: 1*10^11 / 7.5*10^5 = 13., or 13K/message. I'm running
2.2.9 (Ubuntu package). I'll kick the tires and see what happens.
Again, thanks!
-Ken
* Use of term sliderule not intended as a pejorative, but,
Ok - but your sliderule is bent too.
139KB/message looks more correct. I must have had too many 1024's in
there to the first time.
Ken D'Ambrosio wrote:
Thanks for all the pointers! Though I'm afraid your sliderule* dropped a
decimal: 1*10^11 / 7.5*10^5 = 13., or 13K/message. I'm
11 matches
Mail list logo
