Skip to main content
Database Administrators

Return to Question

added 1 character in body; edited tags
Source Link
RolandoMySQLDBA
RolandoMySQLDBA
  • 184.3k
  • 33
  • 323
  • 531

LetsLet's say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance?

Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Lets say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance?

Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Let's say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance?

Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Tweeted twitter.com/#!/StackDBAs/status/274860963621113856
added 2 characters in body; edited tags
Source Link
RolandoMySQLDBA
RolandoMySQLDBA
  • 184.3k
  • 33
  • 323
  • 531

Lets say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance? Then

Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Lets say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance? Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Lets say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance?

Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius

Source Link
Darius
Darius
  • 273
  • 5
  • 8

How much does table size affect performance?

Lets say I have a MyISAM table (amongst other tables) with 2938347 rows. This table is merely being used for logging and doesn't get emptied very often.

By not regularly archiving or deleting these rows, does having this table around affect server performance? Then, what about tables/databases on a MySQL server that are massive in size, but aren't accessed all that often. These tables co-exist with frequently accessed/queried tables, and I'm wondering if they're causing problems or not.

Darius