You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For test_big_containers it would almost never finish because of a bug within the epoll socket (romange/helio#363). After the fix, locally the memory does not surpass 1.4x (dropped from 2x) but it seems that on the CI it still fails with (2x). I also:
compared the INFO MEMORY from both EPOLL and IOURING leading to very similar memory footprints for both variants
calculated the total allocations and deallocations with the memory tracker for both EPOLL and IOURING and both of them had very similar results
I suspect there is something around the EPOLL socket operations that "wastes" memory but we need to somehow narrow it down
The text was updated successfully, but these errors were encountered:
See https://github.com/dragonflydb/dragonfly/actions/runs/12764061257/job/35575450779#step:6:3437
For
test_big_containers
it would almost never finish because of a bug within the epoll socket (romange/helio#363). After the fix, locally the memory does not surpass1.4x
(dropped from 2x) but it seems that on the CI it still fails with (2x). I also:INFO MEMORY
from bothEPOLL
andIOURING
leading to very similar memory footprints for both variantsEPOLL
andIOURING
and both of them had very similar resultsI suspect there is something around the EPOLL socket operations that "wastes" memory but we need to somehow narrow it down
The text was updated successfully, but these errors were encountered: