D simple web server

[gedaiu]

On Tuesday, 3 September 2013 at 18:49:25 UTC, Batuhan Göksu wrote:
> On Tuesday, 3 September 2013 at 15:55:48 UTC, gedaiu wrote:
>> I belive the fails are from the writeln. I made a commit where 
>> i removed them.  Please update the code
>>
>> thanks
>> Bogdan
>>
>>
>> On Tuesday, 3 September 2013 at 15:49:44 UTC, Batuhan Göksu 
>> wrote:
>>> On Tuesday, 3 September 2013 at 15:23:36 UTC, gedaiu wrote:
>>>> Hi,
>>>>
>>>> nice test!
>>>>
>>>> on my computer(linux, i5, 8gb ram) i have these results:
>>>>
>>>> siege -d10 -c50 -t 133s http://localhost:8080/
>>>>
>>>> Transactions:		        1290 hits
>>>> Availability:		      100.00 %
>>>> Elapsed time:		      132.70 secs
>>>> Data transferred:	        0.01 MB
>>>> Response time:		        0.14 secs
>>>> Transaction rate:	        9.72 trans/sec
>>>> Throughput:		        0.00 MB/sec
>>>> Concurrency:		        1.35
>>>> Successful transactions:        1290
>>>> Failed transactions:	           0
>>>> Longest transaction:	       11.42
>>>> Shortest transaction:	        0.00
>>>>
>>>>
>>>> and apache on the same machine has these results:
>>>>
>>>> siege -d10 -c50 -t 133s http://localhost/
>>>>
>>>> Transactions:		        1269 hits
>>>> Availability:		      100.00 %
>>>> Elapsed time:		      132.63 secs
>>>> Data transferred:	        0.32 MB
>>>> Response time:		        0.09 secs
>>>> Transaction rate:	        9.57 trans/sec
>>>> Throughput:		        0.00 MB/sec
>>>> Concurrency:		        0.91
>>>> Successful transactions:        1269
>>>> Failed transactions:	           0
>>>> Longest transaction:	        0.43
>>>> Shortest transaction:	        0.05
>>>>
>>>> Thanks,
>>>> Bogdan
>>>>
>>>> On Tuesday, 3 September 2013 at 14:56:33 UTC, Batuhan Göksu 
>>>> wrote:
>>>>> On Saturday, 31 August 2013 at 16:42:11 UTC, gedaiu wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Because I have a personal project based on a custom web 
>>>>>> server, and I couldn't find one implemented in D(excepting 
>>>>>> vibe.d), I started to implement some web server classes in 
>>>>>> D with the hope that my work will be useful to someone 
>>>>>> else as well. If you are interested in this project, or if 
>>>>>> you want to contribute to it, here is the link to the git 
>>>>>> repository:
>>>>>>
>>>>>> https://github.com/gedaiu/DSWS
>>>>>>
>>>>>> Also, I don't have a lot of experience with D and I would 
>>>>>> apreciate if someone would like to spare some time for a 
>>>>>> code review for my work.
>>>>>>
>>>>>> Thanks,
>>>>>> Bogdan
>>>>>
>>>>> But got a nice progression of application development.
>>>>>
>>>>> HTTP stress test done with Siege.
>>>>>
>>>>> Siege Code : siege -d10 -c50 http://localhost/
>>>>>
>>>>> Transactions:		         156 hits
>>>>> Availability:		       12.69 %
>>>>> Elapsed time:		      133.23 secs
>>>>> Data transferred:	        0.18 MB
>>>>> Response time:		        0.07 secs
>>>>> Transaction rate:	        1.17 trans/sec
>>>>> Throughput:		        0.00 MB/sec
>>>>> Concurrency:		        0.08
>>>>> Successful transactions:    156
>>>>> Failed transactions:	        1073
>>>>> Longest transaction:	        0.33
>>>>> Shortest transaction:	        0.00
>>>
>>>
>>> There's something wrong with these results.
>>> I did it again while writing this post here are the results
>>>
>>> Siege Code : siege -d10 -c50 http://localhost/
>>>
>>> These results have been on the front side with Nginx 
>>> (ProxyPass)
>>>
>>> Please try this way. (Siege Code: http://localhost/ 
>>> siege-d10-c50)
>>>
>>> Last Results
>>> --------------------------------------
>>> Transactions:		         187 hits
>>> Availability:		       14.84 %
>>> Elapsed time:		      133.49 secs
>>> Data transferred:	        0.18 MB
>>> Response time:		        0.10 secs
>>> Transaction rate:	        1.40 trans/sec
>>> Throughput:		        0.00 MB/sec
>>> Concurrency:		        0.14
>>> Successful transactions:         187
>>> Failed transactions:	        1073
>>> Longest transaction:	        0.61
>>> Shortest transaction:	        0.00
>
> Is now running.
>
> The only problem "172 bytes" when it comes to data is 
> collapsing.
>
> HTTP/1.1 502 1.22 secs: 172 bytes ==> GET /

Sorry... but I don't think I understand what you want to say... 
can you give more information about it?

Thanks,
Bogdan