Add performance considerations to README

README.ja.md

@@ -287,6 +287,24 @@ $ vuls tui
 
 ![Vuls-Scan-Flow](img/vuls-scan-flow.png)
 
+----
+# Performance Considerations
+
+- Ubuntu, Debian and CentOS  
+アップデート対象のパッケージが沢山ある場合は、Changelogをパースするので遅いし、スキャン対象サーバのリソースを消費する。
+
+- Amazon, RHEL and FreeBSD  
+高速にスキャンし、スキャン対象サーバのリソース消費量は小さい。
+
+| Distribution|         Scan Speed | Resource Usage On Target Server |
+|:------------|:-------------------|:-------------|
+| Amazon      |               Fast | Light            |
+| RHEL        |               Fast | Light            |
+| FreeBSD     |               Fast | Light            |
+| Ubuntu      |               Slow | Heavy            |
+| Debian      |               Slow | Heavy            |
+| CentOS      |               Slow | Heavy            |
+
 ----
 
 # Use Cases

README.md

@@ -286,6 +286,24 @@ see https://github.com/future-architect/vuls/tree/master/setup/docker
 
 ![Vuls-Scan-Flow](img/vuls-scan-flow.png)
 
+----
+# Performance Considerations
+
+- on Ubuntu, Debian and CentOS  
+Vuls parses a changelog of upgradable packages. The scan speed is slow and resource usage is heavy when there are many updatable packages on target server.  
+
+- On Amazon, RHEL and FreeBSD  
+High speed scan and resource usage is light because Vuls can get CVE IDs by using package manager(no need to parse a changelog).
+
+| Distribution|         Scan Speed | Resource Usage On Target Server |
+|:------------|:-------------------|:-------------|
+| Amazon      |               Fast | Light            |
+| RHEL        |               Fast | Light            |
+| FreeBSD     |               Fast | Light            |
+| Ubuntu      |               Slow | Heavy            |
+| Debian      |               Slow | Heavy            |
+| CentOS      |               Slow | Heavy            |
+
 ----
 
 # Use Cases