Cloud
BB.Cloud - it is your own server instance.
We have monthly plans of BB.Cloud:
Nano, Mini, Start, Pro, Business, Big Business with different power.
- BB.Cloud have big iterations
- BB.General - all resources are shared into all non cloud bots
- BB.Cloud - all resources are shared only between your bots
Cloud | Cost, USD | Monthly iterations |
Cloud.Hobby* | 22 | 1 million |
Cloud.Nano | 33 | 2 million |
Cloud.Mini | 55 | 5 million |
Cloud.Start | 99 | 10 million |
Cloud.PRO | 220 | 45 million |
Cloud.Business | 300 | 100 million |
Cloud.BigBusiness | 440 | 200 million |
Cloud | Approximate iterations: | | |
| daily | minutes | seconds |
Cloud.Hobby* | 32 250 | 22.4 | 0.37 |
Cloud.Nano | 64 500 | 44.8 | 0.74 |
Cloud.Mini | 160 000 | 112 | 1.86 |
Cloud.Start | 320 000 | 224 | 3.73 |
Cloud.PRO | 1 450 000 | 1008 | 16.8 |
Cloud.Business | 2 225 000 | 2240 | 37.33 |
Cloud.BigBusiness | 6 450 000 | 4480 | 74.67 |
Please note: values may differ slightly, both up and down, depending on the bot's response time, the complexity of your commands, etc.
The cloud consists of 6 components - tasks:
- WEB task (processes requests from telegram)
- BJS-runtime task (process BJS)
- other 4 tasks for command repetition, for performing background tasks and for brodcasting
There are only 4 tasks in the Hobby Cloud, not 6.
Depending on the tariff plan, the process count changes for WEB and BJS-runtime.
Plan | Web processes | BJS-runtime processes |
Cloud.Hobby | 1 | 1 |
Cloud.Nano | 1 | 2 |
Cloud.Mini | 2 | 2 |
Cloud.Start | 6 | 3 |
Cloud.PRO | 10 | 5 |
Cloud.Business | 20 | 10 |
Cloud.BigBusiness | 40 | 20 |
As a rule 1 command execution spent 1 iteration.
For example -
/command1:Bot.sendMessage("Hello"); // it is take above 100 ms for execution
// Total time: 100 ms
and
/command2:// bot send 10 messages with "Hello"
Bot.sendMessage("Hello-1"); // 100 ms
Bot.sendMessage("Hello-2"); // + 100 ms
Bot.sendMessage("Hello-3"); // + 100 ms
...
Bot.sendMessage("Hello - 10"); // + 100 ms
// Total time: 1000 ms = 1 sec
/command1 and /command2 spent only 1 iteration. But the second command takes ten times as long to execute.Approx execution time for:
/command1is 0.1 - 0.2 sec/command2is 1 - 1.5 sec
Bot can only execute one command at a time on Nano Cloud
So in 1 second on Nano Cloud we can run:
- above 5 times /command1 (5 iterations per 1 second)
- 1 time only /command2 (1 iteration per 1 second)
So Iterations burns depend from your BJS. So we have approximate daily iterations.
Please look on
/command1 and /command2 again/command1 - can be runned 5 times in 1 second. Five users can run this command in one second /command2 - can be runned 1 times in 1 second only. Only one user can run this command in one second.Example. 5 users run
/command1 at the same time:- bot replied to all users within 1-2 seconds
5 users run
/command2 at the same time:- 1 user have answer after 1 second
- 2 user have answer after 2 seconds
- 3 user have answer after 3 seconds
- last user have answer only after 10 seconds!
How to fix this?
- Don't use too many Bot.sendMessage, Bot.sendKeyboard and etc in one command
- Don't use too many Bot.runCommand or Bot.run in one command or on chain
- Don't use too many Api.xxx methods
Make small commands. Use background tasks with Bot.run and run_after
Your bots will run slower. Timeout errors will occur. You need to upgrade your cloud
Look at the Errors tab. If there are a lot of times, this can be a signal.
Contact your admin. It will provide you with complete statistics with graphs.
- 1 user can run 1000 commands per hour
- 1000 users can run 1 command per hour
This is the same use. We have no limit on the count of users.
Last modified 8mo ago