23 - mylake

“strive 1/21 ~ 1/28”

Use

[gem] faker
[gem] rbkit
[gem] rbkit-client
[gem] oink
- Rails plugin and log parser to help narrow down the source(s) of increased memory usage in rails applications.
[gem] memorylogic
- It worked very well because it adds the process id and memory usage in with EVERY single line logged and at the end of each rails request
[gem] stackprof
[gem] memory_profiler
[gem] derailed_benchmarks

[capistrano] Capistrano 3 Upgrade Guide
[rails] Rails Connection Leak
[web] 為什麼瀏覽器 user-agent string 總是包含 Mozilla/5.0 ?
[web] 如何切割 Microservices
1. 這部份程式的行為是相對獨立的
2. 即將快速發展
3. scope 大 + legacy
[rails memory] Memory constantly increasing in Rails app
1. sessions related?
2. count_objects to display all the objets currently used
3. symbols are keep in memory until your restart ruby. Symbol.all_symbols.size
[rails memory] 不是内存泄漏，而是Bloat
- What Is Bloat? you are loading in too much. Too much what, you ask? Why it’s too much ActiveRecord!
- Detecting Bloat => grep resource /var/log/syslog, The problem is when you have bloat, you start seeing them skyrocket past the memory limits, sometimes multiple times an hour:
- Root Cause
  1. Model.find(:all)
  2. :includes are Including Too Much
  3. :includes on a has_many
  4. @model_instance.relationship
  5. Filtering Records with Ruby Instead of SQL
  6. Evil Callbacks in the Model
  7. Named scopes, default scopes, and has_many relationships that specify :include Where Inappropriate
  8. Use :select When You Must Instantiate Large Quantities of Records
  9. Overfed Feeds
  10. Monster Migrations