Book Image

F# High Performance

By : Eriawan Kusumawardhono
Book Image

F# High Performance

By: Eriawan Kusumawardhono

Overview of this book

F# is a functional programming language and is used in enterprise applications that demand high performance. It has its own unique trait: it is a functional programming language and has OOP support at the same time. This book will help you make F# applications run faster with examples you can easily break down and take into your own work. You will be able to assess the performance of the program and identify bottlenecks. Beginning with a gentle overview of concurrency features in F#, you will get to know the advanced topics of concurrency optimizations in F#, such as F# message passing agent of MailboxProcessor and further interoperation with .NET TPL. Based on this knowledge, you will be able to enhance the performance optimizations when implementing and using other F# language features. The book also covers optimization techniques by using F# best practices and F# libraries. You will learn how the concepts of concurrency and parallel programming will help in improving the performance. With this, you would be able to take advantage of multi-core processors and track memory leaks, root causes, and CPU issues. Finally, you will be able to test their applications to achieve scalability.
Table of Contents (15 chapters)
F# High Performance
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Using F# MailboxProcessor


F# has extensive features of asynchronous operations such as the way it uniquely separates and differentiates from other .NET-managed languages, such as C#/VB, Managed C++, Nemerle, IronPython, and IronRuby. But at the same time, it runs on top of .NET CLR, providing high compatibility with other languages.

F#'s own unique asynchronous features are not just the asynchronous workflows; it has a class that acts as a message passing agent or actor, MailboxProcessor. The MailboxProcessor feature was introduced at the same time as asynchronous workflow was released, and the implementation of MailboxProcessor itself is actually an implementation of a set of asynchronous workflows.

Background case of having message agent

The advantage of having an asynchronous model is the fact that we don't have to wait for the operation or task to be completely finished before doing something else, especially the next operations. The advantage that we don't have to wait for the completion...