good morning!!!!

Skip to content
Snippets Groups Projects
  1. Mar 18, 2019
  2. Mar 06, 2019
  3. Feb 26, 2019
    • Zsolt Felföldi's avatar
      les, les/flowcontrol: improved request serving and flow control (#18230) · c2003ed6
      Zsolt Felföldi authored
      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.
      c2003ed6
  4. Feb 14, 2019
  5. Feb 07, 2019
  6. Jan 24, 2019
  7. Jan 11, 2019
  8. Dec 10, 2018
  9. Nov 26, 2018
    • Sheldon's avatar
      light: odrTrie tryUpdate should use update (#18107) · ca228569
      Sheldon authored
      TryUpdate does not call t.trie.TryUpdate(key, value) and calls t.trie.TryDelete
      instead. The update operation simply deletes the corresponding entry, though
      it could retrieve later by odr. However, it adds further network overhead.
      ca228569
  10. Nov 15, 2018
  11. Oct 08, 2018
  12. Sep 20, 2018
  13. Aug 28, 2018
  14. Aug 21, 2018
  15. Aug 20, 2018
  16. Aug 15, 2018
  17. Jul 24, 2018
  18. Jul 04, 2018
  19. Jul 02, 2018
  20. Jun 12, 2018
  21. Jun 11, 2018
  22. Jun 05, 2018
  23. May 18, 2018
  24. May 14, 2018
  25. May 09, 2018
  26. May 07, 2018
  27. Apr 17, 2018
  28. Mar 27, 2018
  29. Mar 26, 2018
  30. Mar 07, 2018
  31. Mar 02, 2018
  32. Feb 26, 2018
  33. Feb 22, 2018
  34. Feb 14, 2018
Loading