pleroma.git - [no description]

Age	Commit message (Collapse)	Author
2020-10-12	Add missing Copyright headers	Mark Felder

2020-09-16	ConnectionPool Worker: use monitor flush instead of checking ref	rinpatch
	`:flush` removes the DOWN message if one had arrived, so this check should no longer be necessary.
2020-09-11	ConnectionPool: Log possible HTTP1 blocks	rinpatch

2020-09-02	improvements and fixes for http requests	Alexander Strizhakov
	- fix for gun worker termination in some circumstances - pool for http clients (ex_aws, tzdata) - default pool timeouts for gun - gun retries on gun_down messages - s3 upload timeout if streaming enabled
2020-07-28	gun ConnectionPool: Re-add a missing cast for remove_client	rinpatch

2020-07-28	gun ConnectionPool: replace casts with calls	rinpatch
	The slowdown from this is most likely immesurable, however it eliminates possible false positives when tracking dead clients.
2020-07-15	ConnectionPool.Worker: do not stop with an error when there is a timeout	rinpatch
	This produced error log messages about GenServer termination every time the connection was not open due to a timeout. Instead we stop with `{:shutdown, <gun_error>}` since shutting down when the connection can't be established is normal behavior.
2020-07-15	parentheses...	href

2020-07-15	Fix race in enforcer/reclaimer start	href

2020-07-15	Ensure connections error get known by the caller	href

2020-07-15	ConnectionPool.Worker: Open gun conn in continue instead of init	href

2020-07-15	Connection Pool: fix LRFU implementation to not actually be LRU	rinpatch
	The numbers of the native time unit were so small the CRF was always 1, making it an LRU. This commit switches the time to miliseconds and changes the time delta multiplier to the one yielding mostly highest hit rates according to the paper
2020-07-15	Use erlang monotonic time for CRF calculation	rinpatch

2020-07-15	Connection pool: Add client death tracking	rinpatch
	While running this in production I noticed a number of ghost processes with all their clients dead before they released the connection, so let's track them to log it and remove them from clients
2020-07-15	Connection pool: Fix a possible infinite recursion if the pool is exhausted	rinpatch

2020-07-15	Connection pool: implement logging and telemetry events	rinpatch

2020-07-15	Connection Pool: register workers using :via	rinpatch

2020-07-15	Connection pool: Fix race conditions in limit enforcement	rinpatch
	Fixes race conditions in limit enforcement by putting worker processes in a DynamicSupervisor
2020-07-15	Refactor gun pooling and simplify adapter option insertion	rinpatch
	This patch refactors gun pooling to use Elixir process registry and simplifies adapter option insertion. Having the pool use process registry instead of a GenServer has a number of advantages: - Simpler code: the initial implementation adds about half the lines of code it deletes - Concurrency: unlike a GenServer, ETS-based registry can handle multiple checkout/checkin requests at the same time - Precise and easy idle connection clousure: current proposal for closing idle connections in the GenServer-based pool needs to filter through all connections once a minute and compare their last active time with closing time. With Elixir process registry this can be done by just using `Process.send_after`/`Process.cancel_timer` in the worker process. - Lower memory footprint: In my tests `gun-memory-leak` branch uses about 290mb on peak load (250 connections) and 235mb on idle (5-10 connections). Registry-based pool uses 210mb on idle and 240mb on peak load