MySQL性能问题简单查询

时间:2013-06-25 13:06:22

标签: mysql sql linux doctrine-orm debian

我正在尝试在MySQL表上运行一个或多或少的简单查询,其中包含大约100000个条目(大小:2319.58MB;平均行程:24KB前行)。

这是查询:

SELECT 
  n0_.id AS id0, 
  n0_.sentTime AS sentTime1, 
  n0_.deliveredTime AS deliveredTime2, 
  n0_.queuedTime AS queuedTime3, 
  n0_.message AS message4, 
  n0_.failReason AS failReason5, 
  n0_.targetNumber AS targetNumber6, 
  n0_.sid AS sid7, 
  n0_.targetNumber AS targetNumber8, 
  n0_.sid AS sid9, 
  n0_.subject AS subject10, 
  n0_.targetAddress AS targetAddress11, 
  n0_.priority AS priority12, 
  n0_.targetUrl AS targetUrl13, 
  n0_.discr AS discr14, 
  n0_.notification_state_id AS notification_state_id15, 
  n0_.user_id AS user_id16 
FROM 
  notifications n0_ 
  INNER JOIN notification_states n1_ ON n0_.notification_state_id = n1_.id 
WHERE 
  n0_.discr IN (
    'twilioCallNotification', 'twilioSMSNotification', 
    'emailNotification', 'httpNotification'
  ) 
ORDER BY 
  n0_.id desc 
LIMIT 
  25 OFFSET 0

100到200秒之间的查询。

这是表格的创建声明:

CREATE TABLE notifications (
    id INT AUTO_INCREMENT NOT NULL,
    notification_state_id INT DEFAULT NULL,
    user_id INT DEFAULT NULL,
    sentTime DATETIME DEFAULT NULL,
    deliveredTime DATETIME DEFAULT NULL,
    queuedTime DATETIME NOT NULL,
    message LONGTEXT NOT NULL,
    failReason LONGTEXT DEFAULT NULL,
    discr VARCHAR(255) NOT NULL,
    targetNumber VARCHAR(1024) DEFAULT NULL,
    sid VARCHAR(34) DEFAULT NULL,
    subject VARCHAR(1024) DEFAULT NULL,
    targetAddress VARCHAR(1024) DEFAULT NULL,
    priority INT DEFAULT NULL,
    targetUrl VARCHAR(1024) DEFAULT NULL,
    INDEX IDX_6000B0D350C80464 (notification_state_id),
    INDEX IDX_6000B0D3A76ED395 (user_id),
    PRIMARY KEY (id)
)  DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE=InnoDB;

ALTER TABLE notifications ADD CONSTRAINT FK_6000B0D350C80464 FOREIGN KEY (notification_state_id) REFERENCES notification_states (id) ON DELETE CASCADE;
ALTER TABLE notifications ADD CONSTRAINT FK_6000B0D3A76ED395 FOREIGN KEY (user_id) REFERENCES users (id) ON DELETE CASCADE;

这些查询由Doctrine2(ORM)创建。我们在运行Debian 6.0.7的虚拟机(1GB ram,单核)上使用MySQL 5.5.31。为什么查询的性能如此糟糕?它是一个数据库设计错误还是vbox只是为了处理这么大量的数据?

2 个答案:

答案 0 :(得分:2)

在discrimin列上添加索引:

ALTER TABLE `notifications` ADD INDEX `idx_discr` (`discr` ASC) ;

答案 1 :(得分:1)

您通过notifications.discr进行过滤,但似乎没有索引。您是否尝试在其上添加索引?