From 3840459b0aa8c64d1ad81f72ed03fa53f7fee88d Mon Sep 17 00:00:00 2001 From: allburov Date: Fri, 9 Feb 2024 15:11:21 +0700 Subject: [PATCH] [core] add noweb engine performance --- docs/site/content/en/docs/overview/faq.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/site/content/en/docs/overview/faq.md b/docs/site/content/en/docs/overview/faq.md index 04f8bfd6..5837b13a 100644 --- a/docs/site/content/en/docs/overview/faq.md +++ b/docs/site/content/en/docs/overview/faq.md @@ -14,6 +14,7 @@ toc: true --- ## How much CPU and Memory does WhatsApp HTTP API consume? +### WEBJS The benchmark has been made on **Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz**. It may differ from case to case, it depends on usage pattern - how many messages you get, how many send, etc. @@ -26,4 +27,10 @@ It may differ from case to case, it depends on usage pattern - how many messages The nature of WhatsApp HTTP API and its underlying engines - is to run **real** WhatsApp Web version in Chrome and communicate with it to prevent blocking from WhatsApp. It's the reason why it's so demanding on resources. +### NOWEB If you're looking for less resource demanded engine - [have a look at **NOWEB** engine ->]({{< relref "/docs/how-to/engines" >}}) + +The quote from the user: +> The server has 2 CPU and 8GB of memory. +> Today we have 85 session in this instance. +