[DCTPE2011] 8) 多伺服器/高效能的Drupal 主機解決方案--黃雋
3 likes719 views
本文档提供了提升 Drupal 性能的多种策略和建议，包括减少不必要的功能、使用缓存技术、优化服务器设置等。作者强调了识别和解决性能瓶颈的重要性，并提供具体的实战案例来展示改善效果。相关的资源链接和模块推荐也在文档中列出，以便进一步学习和应用。
![[DCTPE2011] 8) 多伺服器/高效能的Drupal 主機解決方案--黃雋](https://image.slidesharecdn.com/drupalperformance-110804000522-phpapp01/85/DCTPE2011-8-Drupal-9-320.jpg)
![# ab -c 100 -t 30 http://netivism.com.tw/
Document Path: /
Document Length: 33246 bytes
Before…
Concurrency Level: 100
Time taken for tests: 30.085 seconds
Complete requests: 130
Failed requests: 0
Write errors: 0
Total transferred: 4992040 bytes
HTML transferred: 4920408 bytes
Requests per second: 4.32 [#/sec] (mean)
Time per request: 23142.220 [ms] (mean)
Time per request: 231.422 [ms] (mean, across
all concurrent requests)
Transfer rate: 162.04 [Kbytes/sec] received](https://image.slidesharecdn.com/drupalperformance-110804000522-phpapp01/85/DCTPE2011-8-Drupal-26-320.jpg)
![# ab -c 100 -t 30 http://netivism.com.tw/
Document Path: /
Document Length: 33246 bytes
After
Concurrency Level: 100
Memcache:
Time taken for tests: 30.021 seconds
Complete requests: 432
Failed requests: 0
Write errors: 0
Total transferred: 14976120 bytes
HTML transferred: 14761224 bytes
Requests per second: 14.39 [#/sec] (mean)
Time per request: 6949.333 [ms] (mean)
Time per request: 69.493 [ms] (mean, across
all concurrent requests)
Transfer rate: 487.16 [Kbytes/sec] received](https://image.slidesharecdn.com/drupalperformance-110804000522-phpapp01/85/DCTPE2011-8-Drupal-27-320.jpg)
![# ab -c 100 -t 30 http://netivism.com.tw/
Document Path: /
Document Length: 33329 bytes
After
Concurrency Level: 100
Boost:
Time taken for tests: 30.009 seconds
Complete requests: 5113
Failed requests: 0
Write errors: 0
Total transferred: 172425088 bytes
HTML transferred: 170310941 bytes
Requests per second: 170.38 [#/sec] (mean)
Time per request: 586.922 [ms] (mean)
Time per request: 5.869 [ms] (mean, across
all concurrent requests)
Transfer rate: 5611.05 [Kbytes/sec] received](https://image.slidesharecdn.com/drupalperformance-110804000522-phpapp01/85/DCTPE2011-8-Drupal-28-320.jpg)
[DCTPE2011] 8) 多伺服器/高效能的Drupal 主機解決方案--黃雋
- 1. Drupal 超速指引 How to Speed Up Drupal 2011 Drupalcamp Taipei Jimmy Huang email: Jimmy at netivism.com.tw blog: jimmyhub.net
- 2. 高效能 Drupal 策略 • 小比大好，少比多好，瘦比胖好 • 不該出現的不要出現 • 不需裝的不要裝 • 不需即時運算的就快取 • 記憶體比資料庫好 • 資料庫比檔案好
- 3. 如何擬定效能改善方針 • 瓶頸在哪裡？ – 慢再哪裡？ CPU / 記憶體 / 流量？ – 哪個頁面發生這個問題？ – 慢再何時？ • 檢測瓶頸 – CPU : 確認是 Apache 還是 MySQL – 記憶體 : 確認沒有用到 Swap 磁區 – 流量 : 確認連線場所網路順暢 – 頁面 : 確認某些頁面特別久
- 4. 如何擬定效能改善方針 ( 續 ) • 哪個網頁特別龜？ • 登入時瀏覽和登出時瀏覽的差異？ • 租用哪家 Server ？有權限做 Server 調整？ • 每日造訪頁數（ awstats / google analytics ） ? • 很多人看？還是很多爬蟲？
- 5. 如何擬定效能改善方針 ( 續 ) • 安裝模組 ex. memcache, boost, csstidy … • 調整 Server ex. Apache MaxClients 數值 ex. Mod Deflate • 調整 Drupal 設定 – 根據檢測出來的頁面，調整對應設定 • 調整程式碼 – 非不得已，自行開發模組，再調整程式碼
- 6. 在 Drupal 如何檢測效能 • Devel 觀察記憶體 / 頁面產生速度 • Devel 蒐集 Database 使用的狀況 • 分析 Query 問題、來源 • 調整出問題之 Views / Panels / 程式碼
- 7. 在 Drupal 如何檢測效能 ( 續 ) garland, system, block, dblog, filter, menu, node, taxonomy, user, content, date, date_api, date_repeat, date_timezone, number, optionwidgets, text, feeds, feeds_ui, feeds_xpathparser, ctools, job_scheduler, devel, views, views_ui
- 8. 在 Drupal 如何檢測效能 ( 續 )
- 10. 檢測效能 – Apache / MySQL
- 11. 檢測效能 – 流量問題
- 12. 檢測效能 – 流量問題
- 13. 實戰 - css / javascript aggregration Before…
- 14. 實戰 - css / javascript aggregration After…
- 15. 實戰 - html / css / javascript 壓縮 Before…
- 16. 實戰 - html / css / javascript 壓縮 (續) After…
- 17. 實戰 - html / css / javascript 壓縮 (續) use: http://www.seoconsultants.com/tools/compression
- 18. 實戰 - html / css / javascript 壓縮 (續) • Apache mod_deflate 開啟 • Page Compression 開啟 • 第三方模組 – Advanced CSS/JS Aggregation – CSS Gzip – CSSTidy
- 19. 實戰 – 快取技術 • Drupal 快取方式 – Menu , Form, Page, Variables, Content, Language … • 快取技術 – Drupal 內建整頁 HTML 快取 – Views / Panels 模組快取 – Boost 模組
- 20. Drupal 頁面快 取
- 21. Views 快取
- 22. Panel 快取
- 23. Boost 快取
- 24. 實戰 – 記憶體快取 • 為何把快取放進記憶體？ – 建立 Database 連線緩慢 – MySQL 的效能不足 – Database 新增、刪除的動作比記憶體慢 • 如何做？ – 安裝 memcached – 安裝 php-memcache – 安裝 drupal memcache
- 25. 實戰 – 記憶體快取
- 26. # ab -c 100 -t 30 http://netivism.com.tw/ Document Path: / Document Length: 33246 bytes Before… Concurrency Level: 100 Time taken for tests: 30.085 seconds Complete requests: 130 Failed requests: 0 Write errors: 0 Total transferred: 4992040 bytes HTML transferred: 4920408 bytes Requests per second: 4.32 [#/sec] (mean) Time per request: 23142.220 [ms] (mean) Time per request: 231.422 [ms] (mean, across all concurrent requests) Transfer rate: 162.04 [Kbytes/sec] received
- 27. # ab -c 100 -t 30 http://netivism.com.tw/ Document Path: / Document Length: 33246 bytes After Concurrency Level: 100 Memcache: Time taken for tests: 30.021 seconds Complete requests: 432 Failed requests: 0 Write errors: 0 Total transferred: 14976120 bytes HTML transferred: 14761224 bytes Requests per second: 14.39 [#/sec] (mean) Time per request: 6949.333 [ms] (mean) Time per request: 69.493 [ms] (mean, across all concurrent requests) Transfer rate: 487.16 [Kbytes/sec] received
- 28. # ab -c 100 -t 30 http://netivism.com.tw/ Document Path: / Document Length: 33329 bytes After Concurrency Level: 100 Boost: Time taken for tests: 30.009 seconds Complete requests: 5113 Failed requests: 0 Write errors: 0 Total transferred: 172425088 bytes HTML transferred: 170310941 bytes Requests per second: 170.38 [#/sec] (mean) Time per request: 586.922 [ms] (mean) Time per request: 5.869 [ms] (mean, across all concurrent requests) Transfer rate: 5611.05 [Kbytes/sec] received
- 29. Before After
- 30. 參考資源 • Web resource – Drupal效能相關模組 (drupal.org) – Drupal效能群組 (group.drupal.org) – Drupal Performance Handbook (drupal.org) – Drupal Performance Tuning (2bits) • Book – Drupal 6 Performance Tips (PACKT) – Drupal Performance and Scalability (Lullabot)