Roman Gershman b7b96424e4 deprecate RecordsPopper and serialize channel records during push (#3667) ... chore: deprecate RecordsPopper and serialize channel records during push Records channel is redundant for DFS/replication because we have single producer/consumer scenario and both running on the same thread. Unfortunately we need it for RDB snapshotting. For non-rdb cases we could just pass a io sink to the snapshot producer, so that it would use it directly instead of StringFile inside FlushChannelRecord. This would reduce memory usage, eliminate yet another memory copy and generally would make everything simpler. For that to work, we must serialize the order of FlushChannelRecord, and that's implemented by this PR. Also fixes #3658. Signed-off-by: Roman Gershman <roman@dragonflydb.io>		2024-09-09 06:19:04 +00:00
..
actions	fix: pytest warnings (#3497)	2024-08-13 16:05:15 +03:00
images	update readme (#794)	2023-02-14 23:08:32 +02:00
ISSUE_TEMPLATE	feat(server): support epoll linux api (#351)	2022-10-04 11:11:09 +03:00
workflows	deprecate RecordsPopper and serialize channel records during push (#3667)	2024-09-09 06:19:04 +00:00
PULL_REQUEST_TEMPLATE.md	docs(PR Template): Add PR Template Enforcing Conventional Commits #107 (#137)	2022-06-12 10:40:17 +03:00