ByteBuffer - Reduce Allocations for Serialization Path #141

File: Utilities/ByteBuffer.cs

PutInt and PutLong both call BitConverter.GetBytes(...) which allocates a new byte[] on every call, then immediately Array.Copy it into the buffer. This is avoidable entirely using BinaryPrimitives and MemoryMarshal from System.Buffers:

// BEFORE - allocates byte[] every call
public void PutLong(long value)
{
    var longAsBytes = BitConverter.GetBytes(IPAddress.NetworkToHostOrder(value));
    Array.Copy(longAsBytes, 0, _internalBuffer, Position, longAsBytes.Length);
    Position += longAsBytes.Length;
}
// AFTER - zero allocation

public void PutLong(long value)

{

BinaryPrimitives.WriteInt64BigEndian(_internalBuffer.AsSpan(Position), value);

Position += sizeof(long);

}
public long GetLong()

{

var result = BinaryPrimitives.ReadInt64BigEndian(_internalBuffer.AsSpan(Position));

Position += sizeof(long);

return result;

}

The IPAddress.HostToNetworkOrder / NetworkToHostOrder dance exists solely to handle big-endian byte ordering — BinaryPrimitives.WriteInt64BigEndian does this directly, with no allocation. This applies equally to PutInt/GetInt. On serialization-heavy workloads this is high-impact.

The ByteBuffer itself could also be refactored to work over Memory<byte> or Span<byte> to allow callers to supply pooled or stack-allocated memory rather than always allocating internally.

Any pull requests addressing this change should provide supporting before and after benchmark results.