The forwarder can currently run only on 64-bit machines.
As LMDB is used for the back-end, buffer file size is limited to 4 GB on 32-bit, but because the forwarder needs additional space to allow for fragmentation - stored data vs. footprint, and to provide adequate additional space when data is received while purging is in progress, the usable buffer space is less.
LMDB is a great storage format for this scenario because of its recovery-free design (vs. others using WAL which may require manual intervention to recover from time to time). That benefit aside, we probably want to use an alternative on 32-bit systems.
The forwarder can currently run only on 64-bit machines.
As LMDB is used for the back-end, buffer file size is limited to 4 GB on 32-bit, but because the forwarder needs additional space to allow for fragmentation - stored data vs. footprint, and to provide adequate additional space when data is received while purging is in progress, the usable buffer space is less.
LMDB is a great storage format for this scenario because of its recovery-free design (vs. others using WAL which may require manual intervention to recover from time to time). That benefit aside, we probably want to use an alternative on 32-bit systems.