We've introduced a 250-millisecond read timeout in our database interactions to increase efficiency and overall system performance.

This timeout is essentially a time limit set for our system to get a response from the database. If the set time limit is exceeded without receiving a response, the read attempt is terminated, returning an error. This mechanism enhances our system's responsiveness and capability to handle numerous queries effectively, minimizing potential waiting times.

Further, we're excited to inform you that we're in the process of transitioning to a faster, more efficient database platform. This upgrade will significantly improve our query processing speed, resulting in better performance and reliability. However, this transition will take some time as we're ensuring a smooth and seamless shift to avoid any potential disruptions to our service. We apologize for any temporary inconvenience this might cause and greatly appreciate your patience during this period.

Dear users,

To optimize our system, we have implemented a 250-millisecond timeout for database read operations. Understanding the possible complexities this could introduce, we would like to provide some recommendations to minimize the risk of timeouts:

Reduce the number of calls to User.getProperty and Bot.getProperty: Try to limit the use of unnecessary variables. The fewer variables requested, the lower the database load, thus reducing the likelihood of a timeout.

Limit the size of variable values: When using functions such as User.setProperty and Bot.setProperty, it's recommended to keep data size minimal. Smaller data volumes process faster, reducing timeout possibilities. Props with data for All bots users - it is not good. Use list here.

Since the beginning of the year, we've seen a substantial 100% increase in traffic. 😱❤️🎉🥳

This growth underscores the necessity of enhancing our system architecture, and we want to assure you that our team is actively working on it.

While we strive to improve our backend, it's also crucial that user-generated code becomes more efficient. An increase in the user base means increased diversity in the code, which can introduce performance bottlenecks, impacting the overall platform speed.

Unfortunately, when user codes are slow, they can impact the platform at large, causing all bots to slow down. As a result, we've had to introduce limits, including the 250-millisecond database read timeout, to maintain BB stability and improve overall performance.

We're continuously looking for ways to balance performance, user experience, and growth, while also maintaining a platform that allows users to build varied and complex bots. We appreciate your understanding and your contributions to improving BB.

We have more good apdex now.

Today we try to increase prop reading timeout for +40% from 250 ms to 350 ms

Once more time. This BJS is NOT working!
DO NOT USE IT!

Yes, it is working with 10 users, maybe 20. But it 100% is not working with 50 or more users!
You will have TimeOut error.

var fullBotUsers = Bot.getProperty("wholeUsers")
for (var index in fullBotUsers) {
  var info = fullBotUsers[index]

Use Bot.runAll

Seems we have huge timeouts with Api.getChatMember for 8 secs.

Please temporary remove this code. You can comment it.
Fix in progress

Bot cloning - fixed

approx 500 tasks for bot cloning in progress now

update: completed

We have this error with Api.getChatMember because it is not only one getChatMember

As a rule it is several commands like:

getChatMember > check > ... > getChatMember > check > 

so you have timeout here because all this commands must be executed in 8 secs only! 🙈


How make quickly work around?

Use Bot.run with runAfter:

getChatMember > runAfter > check > ... getChatMember > runAfter > check >

We will move

getChatMember

to background asap with this issue.

Api.getChatMember is executed now in background with 100 secs timeout
One getChatMember method can take 5 secs so in one command you can check approx 20 channels

It is must be more stable now.

We have a lot of errors in BJS like on success of getChatMember:

BJS error: Cannot read properties of null (reading 'data')

this code can be looks like:

if(request.data){
...
)

There are no any request In success command!
Because user don't post any request to bot: bot make request (with Api.getChatMember or etc) not user.

Simple fix
Fix your code with:

if(request&&request.data){
...
)

Http.get method and another Http methods - timeout increased to 100 secs

This error must be fixed now

Performance work continues. We want to significantly speed up BB.

It is most priority task now.

We are currently actively working on improving our system to ensure faster property retrieval. This update will significantly increase the speed of property reading and enhance overall performance.

We are investing significant efforts into a successful migration to a new and improved database. This process is complex and requires thorough testing to ensure seamless system operation after implementation. We strive for flawless execution of the data unloading mechanism from the old database, so we kindly ask for your patience and await further updates.

Stay tuned to our news as we will regularly provide progress updates and the latest developments. We are committed to providing you with enhanced features and a more efficient user experience with our system. Thank you for your patience and support!

We have good Appdex now 🎉😱

Continue to work and monitoring.
Prop timeout reading will be increased on good Appdex after 24 hours

Most slowly it is BJS-runtime now.

It is:
- database props reading (approx 80%)
- BJS execution

So we need to improve props reading&writing.

Apdex is green for 24 hours. 🎉

Prop timeout reading increased to 1000 ms

#timeout

Deprecated. Google remove it

HTTP requests - fixed and more quick now

Command execution timeout is increased from 8 secs to 10 secs

#timeout