{"id":964,"date":"2010-05-07T11:37:28","date_gmt":"2010-05-07T11:37:28","guid":{"rendered":"http:\/\/www.navision-blog.de\/2010\/05\/07\/using-a-mailboxprocessor-to-speedup-fake-f-make\/"},"modified":"2022-12-29T12:37:39","modified_gmt":"2022-12-29T12:37:39","slug":"using-a-mailboxprocessor-to-speedup-fake-f-make","status":"publish","type":"post","link":"http:\/\/www.navision-blog.de\/blog\/2010\/05\/07\/using-a-mailboxprocessor-to-speedup-fake-f-make\/","title":{"rendered":"Using a MailboxProcessor to speedup “FAKE – F# MAKE”"},"content":{"rendered":"

Earlier today I released \u201cFAKE \u2013 F# Make\u201d version 1.10.0<\/a>. This new release contains a lot path issue fixes for Mono<\/a> and a new architecture for logging and tracing. <\/p>\n

A guy named Joel Mueller had an awesome idea and sent me some patches. He noticed that TraceHelper.fs writes all messages synchronously to the console and\/or a XML output file, which means the actual build operations must wait on the writing of hundreds of trace messages, slowing down the actual build.<\/p>\n

His idea was to use a MailboxProcessor to buffer up the trace messages and write them out asynchronously, so that the actual build can proceed at full speed.<\/p>\n

\n

type<\/span> Message = <\/p>\n

    { Text      : string<\/p>\n

      Color     : ConsoleColor<\/p>\n

      Newline   : bool<\/p>\n

      Important : bool}<\/p>\n

 <\/p>\n

\/\/\/ ….<\/span><\/p>\n

 <\/p>\n

let<\/span> buffer = MailboxProcessor.Start (fun<\/span> inbox -><\/span><\/p>\n

    let<\/span> rec<\/span> loop () = <\/p>\n

        async {<\/p>\n

            let!<\/span> (msg:Message) = inbox.Receive()<\/p>\n

            match<\/span> traceMode with<\/span><\/p>\n

            | Console -><\/span> logMessageToConsole msg<\/p>\n

            | Xml     -><\/span> appendXML msg.Text<\/p>\n

 <\/p>\n

            return!<\/span> loop ()}<\/p>\n

 <\/p>\n

    loop ())      <\/p>\n<\/p>\n<\/div>\n

Now all internal logging and tracing functions can post their their messages to the inbox of the MailboxProcessor:<\/p>\n

\n

\/\/\/ Logs the specified string (via message buffer)<\/span><\/p>\n

let<\/span> logMessage important newLine message =<\/p>\n

    match<\/span> traceMode with<\/span><\/p>\n

    | Console -><\/span><\/p>\n

        { Text = message; <\/p>\n

          Important = important; <\/p>\n

          Newline = newLine; <\/p>\n

          Color = ConsoleColor.White }<\/p>\n

          |> buffer.Post<\/p>\n

    | Xml     -><\/span> <\/p>\n

        { defaultMessage with<\/span> <\/p>\n

            Text = sprintf "<message><![CDATA[%s]]><\/message>"<\/span> <\/p>\n

                     message }<\/p>\n

          |> buffer.Post <\/p>\n<\/p>\n<\/div>\n

This idea reduces the build time of FAKE\u2019s self build from 3 min. to 2 min. Which is really amazing, since I didn\u2019t have to change anything in the build script. This version is compatible to the last released version.<\/p>\n

Please download \u201cFAKE \u2013 F# Make\u201d version 1.10.0<\/a> and tell me what you think.<\/p>\n

https:\/\/edpillgrece.gr<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"

Earlier today I released \u201cFAKE \u2013 F# Make\u201d version 1.10.0. This new release contains a lot path issue fixes for Mono and a new architecture for logging and tracing. A guy named Joel Mueller had an awesome idea and sent me some patches. He noticed that TraceHelper.fs writes all messages synchronously to the console and\/or […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[448,546],"tags":[664,545,544,149],"_links":{"self":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/964"}],"collection":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/comments?post=964"}],"version-history":[{"count":1,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/964\/revisions"}],"predecessor-version":[{"id":2037,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/posts\/964\/revisions\/2037"}],"wp:attachment":[{"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/media?parent=964"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/categories?post=964"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.navision-blog.de\/blog\/wp-json\/wp\/v2\/tags?post=964"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}