<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi all,<br class=""><br class="">Sorry I didn't have much time and therefore could only do a mostly search and replace mess [1].<br class="">I think I eliminated most retain/releases. I'm not sure if it actually works but the benchmark produces a number and the tests are happy. But I'd be very worry about it actually working! Seriously if anyone considers using it, please review the code. I have just tried to improve it pretty much mechanically. I haven't actually fully read the code.<br class=""><br class="">But before (on my machine)<br class="">--- SNIP ---<br class="">$ .build/release/bench<br class="">Benchmark result:<br class="">Took 7.7 seconds to run<br class="">648582.28 req/sec<br class="">--- SNAP ---<br class=""><br class="">after<br class="">--- SNIP ---<br class="">$ .build/release/bench<br class="">Benchmark result:<br class="">Took 5.27 seconds to run<br class="">948171.8 req/sec<br class="">--- SNAP ---<br class=""><br class="">which is almost 50% more reqs/s.<br class=""><br class="">- The reason there was plenty of ref counting done is that it used to use classes. I changed everything to structs (inout where necessary) and also switched from String to StaticString.<br class="">- it also used protocols as types like 'func foo(x: SomeProtocl)' that always comes with a protocol witness table which is bad for performance too<br class="">- I also eliminated copies of values that aren't necessary.<br class="">- I think generally it's now much more inline with the C version<br class=""><br class="">Any questions please let me know. The full diff can be found here [1].<br class=""><br class="">And again, I'm not saying I turned this into great Swift or anything. It's just meant as a demonstration that you can get rid of the reference counting overhead if you switch to value types. If you need reference semantics but don't want to pay the reference counting overhead I guess UnsafePointer<> and friend work which obviously comes with some drawbacks.<br class=""><br class="">All in all I don't see much value in translating the C version to Swift. The C version gets updated, the Swift version then constantly needs to replicate these changes. And given that Swift has excellent C calling capabilities, why not just stick to the C version?<br class=""><br class="">[1]: <a href="https://github.com/smithmicro/HTTPParser/pull/1/files" class="">https://github.com/smithmicro/HTTPParser/pull/1/files</a><br class=""><br class="">Cheers,<br class=""> Johannes<div class=""><img apple-inline="yes" id="87502EFE-E892-455E-83FE-5E39FBF32CB4" src="cid:0E370231-3F7A-4A1D-B601-8742826F0012" class=""><br class=""><blockquote type="cite" class="">On 23 Nov 2016, at 17:51, David Sperling via swift-server-dev <swift-server-dev@swift.org> wrote:<br class=""><br class="">Here are the steps for those that want to review the performance of HTTPParser.<br class=""> <br class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• git clone https://github.com/smithmicro/HTTPParser.git<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• in the directory, run “swift package generate-xcodeproj”<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• open HTTPParser.xcodeproj in Xcode 8.1<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Select “bench” from the target dropdown list<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Select Profile from the Product menu<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Choose Time Profiler, then record<br class=""></div> <br class="">Attached is a screenshot showing 5.5% being spent in swift_release, and 2.7% percent in swift_bridgeObjectRetain.<br class=""> <br class="">I will be interesting to try the suggestions that Helge has pointed out here:<br class="">https://github.com/swift-server/work-group/pull/52<br class=""> <br class="">Dave<br class=""> <br class="">P.S. If you want to just run the program in Xcode to see the performance, switch to Release build configuration.<br class=""> <br class=""> <br class=""><span id="cid:image001.png@01D2456F.20C20BC0"><image001.png></span><br class=""> <br class=""> <br class="">From: <swift-server-dev-bounces@swift.org> on behalf of Michael Gottesman via swift-server-dev <swift-server-dev@swift.org><br class="">Reply-To: Michael Gottesman <mgottesman@apple.com><br class="">Date: Monday, November 21, 2016 at 3:38 PM<br class="">To: Chris Bailey <BAILEYC@uk.ibm.com><br class="">Cc: "swift-server-dev@swift.org" <swift-server-dev@swift.org><br class="">Subject: Re: [swift-server-dev] HTTP Parser<br class=""> <br class=""> <br class=""><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">On Nov 21, 2016, at 5:55 AM, Chris Bailey via swift-server-dev <swift-server-dev@swift.org> wrote:<br class=""> <br class="">>> But it sounds like MIT licensed code can’t be used as part of the effort, maybe that should be added the the front-page of the effort. <br class=""><br class="">I'm not 100% convinced this is true. There's nothing (legally) preventing the inclusion of MIT licensed code in a Apache 2.0 licensed product, you just may have to list some Product Unique Terms (PUTs) to cover it - we don't need the Node.js community to dual-license it for us to use it. Parts of the Swift toolchain already have compiled-in dependencies on MIT licensed code, so my guess is that ship has already sailed on using non-Apache 2.0 licensed code. <br class=""><br class="">Having said that, we'd obviously need a read and approval from the Swift Core Team (and Apple legal!) before making a compiled-in dependency on anything.<br class=""></blockquote> <br class="">We want a consistent license over the entire code base. I imagine we will make an external test suite that will be in a different repository so this will not be an issue.<br class=""> <br class="">Originally we put the swift perf test suite in the swift tree since people kept on breaking it. Since we use PR testing this is no longer an issue (the benchmarks are built as apart of the PR testing). There are some questions around how this is done/who is it done by/when is it down, that will need to be answered before I can move forward with this.<br class=""> <br class="">Michael<br class=""><br class=""><br class=""><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite"><br class="">Chris <br class=""><br class=""><br class=""><br class="">From: Helge Heß via swift-server-dev <swift-server-dev@swift.org> <br class="">To: "swift-server-dev@swift.org" <swift-server-dev@swift.org> <br class="">Date: 20/11/2016 18:08 <br class="">Subject: Re: [swift-server-dev] HTTP Parser <br class="">Sent by: swift-server-dev-bounces@swift.org<br class=""><br class=""><br class=""><br class="">Hi Dave,<br class=""><br class="">thanks for your post, this detail is indeed quite helpful.<br class=""><br class="">I don’t think anyone seriously suggested using a Swift port of the http_parser but instead just the upstream C one. But it sounds like MIT licensed code can’t be used as part of the effort, maybe that should be added the the front-page of the effort.<br class=""><br class="">I assume it is not a huge issue though as a libhttp_parser can be shipped separately from Swift itself, similar to what you would do for OpenSSL etc (and what is already being done with libcurl on Linux).<br class=""><br class="">In any case: Whatever is decided, it at least establishes a performance characteristic, I think any replacement should accomplish a comparable one - preferably faster of course :-)<br class=""><br class="">hh<br class=""><br class=""><br class="">> On 20 Nov 2016, at 16:58, David Sperling via swift-server-dev <swift-server-dev@swift.org> wrote:<br class="">> <br class="">> I would like to provide some additional detail to the discussion on November 4 (which I missed since I joined recently).<br class="">> <br class="">> The team pointed out this thread in Kitura which I initially opened:<br class="">> https://github.com/IBM-Swift/Kitura-net/issues/52<br class="">> <br class="">> Here is the referenced Swift http_parser project which I initially ported as a thought experiment. The goals, API and performance are described in the readme.<br class="">> https://github.com/smithmicro/HTTPParser<br class="">> <br class="">> Michael Gottesman from Apple (@gottesmm) contacted me 2 weeks ago to see if we could add the project into the Swift Benchmark Suite. See the bottom of this PR for the request:<br class="">> https://github.com/IBM-Swift/Kitura-net/pull/55<br class="">> <br class="">> Michael and I approached the Node.js Foundation to see if they were willing to dual license http_parser under Apache 2 so it would be compatible with the Swift license. Here is that discussion, but in summary, a dual license is not realistic.<br class="">> https://github.com/nodejs/http-parser/issues/344<br class="">> <br class="">> So, a http_parser Swift port:<br class="">> - Would not have the proper license to be included in Swift<br class="">> - Does not take full advantage of Swift<br class="">> - Has the issues previously pointed out (UnsafePointers, asserts, throws simulating gotos)<br class="">> - Does, however, demonstrate a Swift HTTP parser performance of 500K requests per second<br class="">> <br class="">> <br class="">> Looking forward to meeting everyone on our call tomorrow. Hopefully this detail was helpful.<br class="">> <br class="">> <br class="">> Dave Sperling<br class="">> Smith Micro<br class=""><br class="">_______________________________________________<br class="">swift-server-dev mailing list<br class="">swift-server-dev@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-server-dev<br class=""><br class=""><br class=""><br class="">Unless stated otherwise above:<br class="">IBM United Kingdom Limited - Registered in England and Wales with number 741598. <br class="">Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU<br class="">_______________________________________________<br class="">swift-server-dev mailing list<br class="">swift-server-dev@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-server-dev<br class=""></blockquote><br class=""><br class="">_______________________________________________<br class="">swift-server-dev mailing list<br class="">swift-server-dev@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-server-dev<br class=""></blockquote><br class=""></div></body></html>