# \[Discussion\] Server Logging API

**URL:** <https://forums.swift.org/t/discussion-server-logging-api/18834>\
**Category:** Proposals\
**Created:** [December 15, 2018, 12:16pm UTC](https://forums.swift.org/t/discussion-server-logging-api/18834 "2018-12-15T12:16:00Z")\
**Posts on this page:** 1\
**Showing post:** 45

<div class="post-metadata">

**Author:** ![johannesweiss](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/johannesweiss/32/38183_2.png) [@johannesweiss](https://forums.swift.org/u/johannesweiss)\
**Post date:** [December 18, 2018, 9:08am UTC](https://forums.swift.org/t/discussion-server-logging-api/18834/45 "2018-12-18T09:08:49Z")

</div>

> [@tomerd](#):
>
> os\_log has serious performance optimizations on darwin, so if you are building an iOS or macOS app you should use it and not worry about this API

Indeed. We should however point out that when [this](https://forums.swift.org/t/custom-string-interpolation-and-compile-time-interpretation-applied-to-logging/18799) lands, we should be able to adopt a few of the osLog optimisations for the server logging effort too and you should then be able to use osLog as a backend (LogHandler) with acceptable performance. Plain osLog however will always remain faster as it decides many things at compile-time that we will need to do at runtime because the server world needs more flexibility.

---

_[View the full topic](https://forums.swift.org/t/discussion-server-logging-api/18834)._