7sharp9's blog
A cup of tea would restore my normality. - Douglas Adams
agents ast async concurrency csharp elixir elm fable fsharp functional-programming fuse games ios javascript mac mailboxprocessor metaprogramming microsoft mono monodevelop monogame monotouch myriad performance quotations running sockets threading tpl tpl-dataflow typeproviders videos xamarin youtube

© 2011 - 2020 7sharp9

Powered by Hugo with theme Dream.

flame on

flame on

Sunday, May 29, 2016

@ 7sharp9

A few weeks back I posted on Twitter that I was experimenting with flame graphs, In this post I will share how this was accomplished.

Black-Scholes Taste Test

Black-Scholes Taste Test

Sunday, Mar 11, 2012

@ 7sharp9

In this edition we are going to be doing a taste test, C# vs F#. Oh yeah, if you quickly glanced at the title you may have thought this was a recipe for black scones, as interesting and tasty as that may be, unfortunately its going to be finance related. I recently presented a paper on the benefits of F#, part of this was a comparison of the famous Black-Scholes equation in both C# and F#.
Fixing a hole...

Fixing a hole...

Sunday, Dec 11, 2011

@ 7sharp9

Due to popular demand… well, I had a couple of requests anyway :-) Heres a post inspired by my recent encounters profiling some of the code in Fracture-IO. I have recently been profiling the code in fracture to remove any so called low hanging fruits. During this time I also noticed an increase in memory allocation. I remembered I had recently been experimenting in a branch using pipelets as a buffer between the send and receive stages in the Http Server, so I set up a simple test to see if pipelets were contributing to the memory allocation issues I was seeing.
 Agents and ObjectPools

Agents and ObjectPools

Sunday, Jun 5, 2011

@ 7sharp9

Everyone knows F# agents are cool right? Well here’s yet another example of how versatile they can be… There was a series of posts last April by Stephen Toub from the pfxteam at Microsoft. I was reading through some of the posts again the other day and thought some of the ideas presented there would make interesting projects in F# to demonstrate the flexibility and succinctness of the language. I thought the ObjectPool example would make an interesting project in F# using agents aka MailboxProcessors.
Sockets and Bockets 4

Sockets and Bockets 4

Friday, Jan 28, 2011

@ 7sharp9

Welcome to part 4 If you were looking forward to some exciting new F# code this time your going to be disappointed, however if you are like me and like looking at graphs and stats and digging in deeper into the code then your going to enjoy this, lets get started…I set up a 5 minute test with 50 clients connecting to the server with a 15ms interval between each one.
Sockets and Bockets 3

Sockets and Bockets 3

Thursday, Jan 20, 2011

@ 7sharp9

Welcome to part three! As promised heres a description of the inner workings. I’m sick to death of typing SocketAsyncEventArgs so from now on I will refer to it as SAEA.BocketPool The BocketPool has an interesting name and with it an interesting constructor! It takes the following parameters: number: The number of items to create in the BocketPool. size: The size of each buffer in bytes. callback: A callback function which is invoked whenever the SAEA object completes its operation.
Sockets and Bockets 2

Sockets and Bockets 2

Friday, Jan 14, 2011

@ 7sharp9

Welcome to part two Lets jump in at the deep end and take a look at some code… When you look at the method syntax for the xxxAsync methods you will notice they return a boolean value that indicates if the method completed synchronously, this means that you have to check the return value every time you use one of the methods and invoke the callback yourself if it completes synchronously.
Sockets and Bockets 1

Sockets and Bockets 1

Thursday, Jan 13, 2011

@ 7sharp9

Welcome to part 1 A while back I read an interesting article by Brian McNamara f-async-on-the-server-side which describes C# and F# versions of a simple asynchronous socket server, one of the driving forces behind the article was how F# can wrap the traditional asynchronous model with Asynchronous Workflows, this produces nice clean simple code compared to the C# version which uses lambda expressions, the code looks quite ugly in this style!

About Me

Hi, my name is Dave Thomas and Im a software engineer from the Uk. I work primarily in F# but also like to tinker with pretty much any interesting language. Im drawn to more functional languages like F#, Swift and Rust.

Have questions or suggestions? Feel free to ask me on Twitter.

Thanks for reading!

Dave Thomas