Maximum OneBox OS System Performance
There is a question about maximum performance. For example, can OneBox OS handle the load of introducing checkouts from one or more supermarkets like Billa?
For example, 10 cashiers are selling at the same time, every 2 minutes a new check, goods arrive at the warehouse and they are accepted, accountants and financiers run their reports, calculate salaries and there is integration with 1C, power bi? Well, for example, 1000 operations per minute?
It's just a matter of not only the power of the servers, but how much the software is able to use the performance of multi-core systems. How thick is the client in the client-server system.
If somehow you can calculate the performance - I will be grateful for the answer.
Original question is available on version: ru
For example, 10 cashiers are selling at the same time, every 2 minutes a new check, goods arrive at the warehouse and they are accepted, accountants and financiers run their reports, calculate salaries and there is integration with 1C, power bi? Well, for example, 1000 operations per minute?
It's just a matter of not only the power of the servers, but how much the software is able to use the performance of multi-core systems. How thick is the client in the client-server system.
If somehow you can calculate the performance - I will be grateful for the answer.
Answers:
OneBox OS is one of the few systems on the market that can scale horizontally.
Here I talked a little about it - https://crm-onebox.com/en/support/onebox-purchase-and-rates/10164-perehod-na-os/
If we talk specifically about the supermarket chain, then:
1. onebox does not have its own thick client (yet), everything happens through a thin client.
2. onebox is not a cash register software. Where is it more correct to use offline thick cash register software at cashier points, and drag data from / to OneBox. For such a model, OneBox fits perfectly, because see point 3
3. onebox has a very fast API https://crm-onebox.com/ru/app/app-api-v2/
There is an API operation mode when the data runs through redis. In this configuration, we can process 10,000 requests/second (10,000 checks). In peaks - even more.
4. onebox can be placed not on one server, but on several at once (horizontally). That is, you can make a cluster for the base, as well as put at least 100 web servers to serve requests from users or API integrations.
5. onebox can be sharded into separate entities through the network application. That is, you can make sure that each store has its own box, while there is a certain chief who manages everything. Here is an example - https://crm-onebox.com/ru/support/onebox-purchase-and-rates/10164-perehod-na-os/
What is described in the topic above is not a problem, it is far from the limit.
1000 operations per second (not even per minute) is the basic performance of OneBox OS if you deploy it even on one server with this configuration https://www.hetzner.com/dedicated-rootserver/ax101
Here I talked a little about it - https://crm-onebox.com/en/support/onebox-purchase-and-rates/10164-perehod-na-os/
If we talk specifically about the supermarket chain, then:
1. onebox does not have its own thick client (yet), everything happens through a thin client.
2. onebox is not a cash register software. Where is it more correct to use offline thick cash register software at cashier points, and drag data from / to OneBox. For such a model, OneBox fits perfectly, because see point 3
3. onebox has a very fast API https://crm-onebox.com/ru/app/app-api-v2/
There is an API operation mode when the data runs through redis. In this configuration, we can process 10,000 requests/second (10,000 checks). In peaks - even more.
4. onebox can be placed not on one server, but on several at once (horizontally). That is, you can make a cluster for the base, as well as put at least 100 web servers to serve requests from users or API integrations.
5. onebox can be sharded into separate entities through the network application. That is, you can make sure that each store has its own box, while there is a certain chief who manages everything. Here is an example - https://crm-onebox.com/ru/support/onebox-purchase-and-rates/10164-perehod-na-os/
What is described in the topic above is not a problem, it is far from the limit.
1000 operations per second (not even per minute) is the basic performance of OneBox OS if you deploy it even on one server with this configuration https://www.hetzner.com/dedicated-rootserver/ax101
19.08.2021, 12:49
Как со мной связаться - никак :)Задавайте вопросы на форуме публично - и я отвечу.
Подробнее - 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
