What are the limitations of OneBox OS
2022-11-18 12:19:01
What are the limitations (in an exhaustive list) in OneBox OS?
Those. we need to understand all the key quantifiable parameters of the system,
upon reaching or exceeding which, the operation of the system will not be possible, or it will be significantly hindered.
For example (not limited to): database size, number of requests and other events received from other systems,
the number of processes in the system, the number of users, etc.
The number of ticks in the system, with the preservation of performance.
The action of searching for a parent among how many processes when comparing fields of the list type, while maintaining the exchange of 100 tickets per second.
Original question is available on version: ru
Those. we need to understand all the key quantifiable parameters of the system,
upon reaching or exceeding which, the operation of the system will not be possible, or it will be significantly hindered.
For example (not limited to): database size, number of requests and other events received from other systems,
the number of processes in the system, the number of users, etc.
The number of ticks in the system, with the preservation of performance.
The action of searching for a parent among how many processes when comparing fields of the list type, while maintaining the exchange of 100 tickets per second.
Answers:
OneBox Corp.
OneBox CORP wrote:
What are the limitations (in an exhaustive list) in OneBox OS?
no such list
OneBox Corp.
OneBox CORP wrote:
For example (not limited to): database size, number of requests and other events received from other systems,
the number of processes in the system, the number of users, etc.
there are projects with tens of millions of orders, they work normally without visible delays (to be more precise, this is 26kkk orders). The same applies to users (10kkk).
The database is divided into tables, there are conditionally no restrictions on its volume.
Having a good server, you can easily create hundreds of new orders per second and have under a hundred million processes, while the system will not fail. If there are any delays on the pages or in the api, this is all very easy to optimize.
Also in boxing it is possible to separate different departments of the company into different systems and synchronize them with each other (send documents, tasks, payments, contacts, etc.) so you can scale without any additional software at all. load on the system.
18.11.2022, 13:09
Original comment available on version: ru
I will add:
Box - restrictions are imposed only by the server on which you install OneBox. The server is your choice.
Cloud - restrictions are imposed by the cloud servers on which OneBox is installed. The allocated resources strongly depend on the tariff.
Since OneBox is mostly a constructor, everything depends heavily on the combination of actions and procedures that are hung on the stages.
OneBox is designed so that for a server like https://www.hetzner.com/dedicated-rootserver/ax101 you can easily upload 100M contacts and 100M orders. And it will bring down the API at 5000 orders per second.
But, if the action "knock somewhere in the external API" is added to the insertion of an order, the speed will drop dramatically.
If you add 50 different actions to "calculate prices" - the speed will drop too.
If there are no actions, there will be thousands of processing per second, if not tens of thousands.
---
The search is almost everywhere used by fulltext, there by the complexity of Log (N).
That is, that there are 1 million orders in the search, that 10M - the difference for the search is not significant.
---
Better give a specific case of what and how you want to use.
Box - restrictions are imposed only by the server on which you install OneBox. The server is your choice.
Cloud - restrictions are imposed by the cloud servers on which OneBox is installed. The allocated resources strongly depend on the tariff.
Since OneBox is mostly a constructor, everything depends heavily on the combination of actions and procedures that are hung on the stages.
OneBox is designed so that for a server like https://www.hetzner.com/dedicated-rootserver/ax101 you can easily upload 100M contacts and 100M orders. And it will bring down the API at 5000 orders per second.
But, if the action "knock somewhere in the external API" is added to the insertion of an order, the speed will drop dramatically.
If you add 50 different actions to "calculate prices" - the speed will drop too.
If there are no actions, there will be thousands of processing per second, if not tens of thousands.
---
The search is almost everywhere used by fulltext, there by the complexity of Log (N).
That is, that there are 1 million orders in the search, that 10M - the difference for the search is not significant.
---
Better give a specific case of what and how you want to use.
18.11.2022, 21:03
Как со мной связаться - никак :)Задавайте вопросы на форуме публично - и я отвечу.
Подробнее - https://1b.app/ru/user/11/ Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
