What's the performance overhead of Log4Net Appender on my .NET application?
<5 milliseconds per log entry (synchronous), <1 millisecond (asynchronous with AsyncAppender wrapper). Nodinite appender sends logs via HTTP POST to Log API synchronously by default—blocks logging thread until HTTP response received (typically 3-5 milliseconds over LAN, 10-20 milliseconds over WAN). For high-throughput applications (>100 logs/second), use Log4Net AsyncAppender wrapper to queue logs in memory and send asynchronously (eliminates blocking, <1 millisecond overhead per log): <appender name="AsyncNodinite" type="log4net.Appender.AsyncAppender"><appender-ref ref="NodiniteAppender"/><bufferSize value="500"/></appender>. Buffer size: 500 logs default (flushes to Nodinite every 500 logs or 30 seconds, whichever first), configurable (increase to 1,000 for higher throughput, decrease to 100 for lower latency). Network failure: If Nodinite Log API unavailable, AsyncAppender drops oldest logs from buffer when full (prevents memory exhaustion), logs warning to local file appender (fallback). Best practice: Configure both Nodinite appender (centralized logging) AND local RollingFileAppender (fallback for network outages) to prevent data loss.
Related Questions
See all FAQs: [Troubleshooting Overview][]