540co/yourTwapperKeeper

MySQL Caching Best Practices

Closed this issue · 2 comments

audvin commented

With close to 30M tweets in the database and perhaps around 1000-2000 keywords active in the stream, how should one configure MySQL for optimal performance.

I've got a server, 1GB memory, the MySQL process consumes about 75% CPU, the stream process gets the rest.

Looking at phpMySQL Status, there are many "red numbers" from the last 30 days...

  • Handler_read_rnd: 16M
  • Handler_read_rnd_next: 8,169M
  • Created_tmp_disk_tables: 47
  • Key_reads: 491M
  • Opened_tables: 7,420M
  • Table_locks_waited: 589k

How should MySQL be configured for best results with yourTwapperKeeper?

jobrieniii commented

Audun,
I personally have never done any MySQL tuning on any yTK instances, so hopefully someone else can chime in...

Sorry,
John

audvin commented

Thanks John,

I guess more RAM is always better, I'm just hoping there's some other ways to increase the milage :)

Audun

On Feb 19, 2012, at 11:18 AM, John OBrien III wrote:

Audun,
I personally have never done any MySQL tuning on any yTK instances, so hopefully someone else can chime in...

Sorry,
John

Reply to this email directly or view it on GitHub:
https://github.com/jobrieniii/yourTwapperKeeper/issues/2#issuecomment-4044330