-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve offer publishing #4950
Improve offer publishing #4950
Conversation
The delay was too long. Some users have 100 - 200 offers and with the 700 ms delay it takes 70-140 sec. This causes more stress for the network and UI due permanent adding of offers. We decreased delay to 30 ms per offer. So with 200 offers it would be about 6 sec. Maybe we could reduce it even further but as it is hard to test in the live network with so many offers it is better to not be too radical with the change.
Invert the if branch so the normal case is first Add comment
Call flush at openOfferManager shutdown. Remove unused method. Force broadcaster to send out immediately, otherwise we could have a 2 sec delay until the bundled messages sent out.
This version is intended to be deployed to a power user to actually try it out live as testing it with real conditions is very difficult.
Travis is failing because of broken Tests. |
@sqrrm Could you please review the changes so it can be added to the release branch asap? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Best wait to merge to master until it's been tested
The periodicRefreshOffersTimer gets started at offer publishing. Before the stopPeriodicRefreshOffersTimer got overwritten by the start in offer publishing so it did not had any effect beside that we restarted it. Now we process offer publishing without delay and a stop after the call would stop the refresh timer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Good find
Change handling of delay at republishing
The delay was too long. Some users have 100 - 200
offers and with the 700 ms delay it takes 70-140 sec.
This causes more stress for the network and UI due
permanent adding of offers. We decreased delay to 30 ms per offer.
So with 200 offers it would be about 6 sec. Maybe we could reduce
it even further but as it is hard to test in the live network with
so many offers it is better to not be too radical with the change.