The situation is remedied for anon access by enabling Drupal cache. SELECT source FROM url_alias WHERE alias = :alias AND language IN (:language, :language_none) ORDER BY language ASC, pid DESC SELECT cid, data, created, expire, serialized FROM cache WHERE cid IN (:cids_0) SELECT cid, data, created, expire, serialized FROM cache_bootstrap WHERE cid IN (:cids_0)ĥ75.825 DrupalDatabaseCache::getMultipleP A Eġ3.585 DrupalDatabaseCache::getMultipleP A EĤ66.9914 DrupalDatabaseCache::getMultipleP A E The wierd thing is that for a single page load about 2/3 of queries are fast, others are exceedingly slow: 1.765 DrupalDatabaseCache::getMultipleP A E I have checked DNS resolution and there should be none either from Drupal side (db host is given by ip, there is a dns entry in /etc/hosts file) nor from MySQL side (skip-name-resolve is on, drupal client is granted access by ip address).Įxecuted 336 queries in 5993.89 ms. After research here and elsewhere I understand that the problem is with the fact that SQL is accessed via network interface, which Drupal apparently does really badly. The Drupal website is currently under development, therefore there is practically no traffic, however, despite ping and shell access being lightning fast, the Drupal site is running extremely slowly (>5 sec to load any page). We have Drupal 7 on Ubuntu LTS virtual machine (VMWare) with MySQL 5.1 server on the same physical server, but on a different virtual machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |