3 Commits (8cde2966af916d85805a47a4350f3567d9e51dbe)

Author	SHA1	Message	Date
Felföldi Zsolt	bddf5aaa2f	les/utils: protect against WeightedRandomSelect overflow (#21839) ... Also fixes a bug in les/flowcontrol that caused the overflow.	4 years ago
Felföldi Zsolt	b4a2681120	les, les/lespay: implement new server pool (#20758) ... This PR reimplements the light client server pool. It is also a first step to move certain logic into a new lespay package. This package will contain the implementation of the lespay token sale functions, the token buying and selling logic and other components related to peer selection/prioritization and service quality evaluation. Over the long term this package will be reusable for incentivizing future protocols. Since the LES peer logic is now based on enode.Iterator, it can now use DNS-based fallback discovery to find servers. This document describes the function of the new components: https://gist.github.com/zsfelfoldi/3c7ace895234b7b345ab4f71dab102d4	4 years ago
gary rong	f78ffc0545	les: create utilities as common package (#20509) ... * les: move execqueue into utilities package execqueue is a util for executing queued functions in a serial order which is used by both les server and les client. Move it to common package. * les: move randselect to utilities package weighted_random_selector is a helpful tool for randomly select items maintained in a set but based on the item weight. It's used anywhere is LES package, mainly by les client but will be used in les server with very high chance. So move it into a common package as the second step for les separation. * les: rename to utils	5 years ago
Felföldi Zsolt	c2003ed63b	les, les/flowcontrol: improved request serving and flow control (#18230) ... This change - implements concurrent LES request serving even for a single peer. - replaces the request cost estimation method with a cost table based on benchmarks which gives much more consistent results. Until now the allowed number of light peers was just a guess which probably contributed a lot to the fluctuating quality of available service. Everything related to request cost is implemented in a single object, the 'cost tracker'. It uses a fixed cost table with a global 'correction factor'. Benchmark code is included and can be run at any time to adapt costs to low-level implementation changes. - reimplements flowcontrol.ClientManager in a cleaner and more efficient way, with added capabilities: There is now control over bandwidth, which allows using the flow control parameters for client prioritization. Target utilization over 100 percent is now supported to model concurrent request processing. Total serving bandwidth is reduced during block processing to prevent database contention. - implements an RPC API for the LES servers allowing server operators to assign priority bandwidth to certain clients and change prioritized status even while the client is connected. The new API is meant for cases where server operators charge for LES using an off-protocol mechanism. - adds a unit test for the new client manager. - adds an end-to-end test using the network simulator that tests bandwidth control functions through the new API.	6 years ago
GagziW	7c02933275	les: changed if-else blocks to conform with golint (#16658)	6 years ago
Zsolt Felfoldi	3e617f3cd6	les: implement light server pool	8 years ago