Home/ Questions/Q 112467
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T02:32:57+00:00

Lets say I wanted to scrape a webpage, and extract some data. I’d most

  • 0

Lets say I wanted to scrape a webpage, and extract some data. I’d most likely write something like this:

let getAllHyperlinks(url:string) =     async {  let req = WebRequest.Create(url)              let! rsp = req.GetResponseAsync()              use stream = rsp.GetResponseStream()             // depends on rsp              use reader = new System.IO.StreamReader(stream)  // depends on stream              let! data = reader.AsyncReadToEnd()              // depends on reader              return extractAllUrls(data) }                    // depends on data

The let! tells F# to execute the code in another thread, then bind the result to a variable, and continue processing. The sample above uses two let statements: one to get the response, and one to read all the data, so it spawns at least two threads (please correct me if I’m wrong).

Although the workflow above spawns several threads, the order of execution is serial because each item in the workflow depends on the previous item. Its not really possible to evaluate any items further down the workflow until the other threads return.

Is there any benefit to having more than one let! in the code above?

If not, how would this code need to change to take advantage of multiple let! statements?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. The key is we are not spawning any new threads. During the whole course of the workflow, there are 1 or 0 active threads being consumed from the ThreadPool. (An exception, up until the first ‘!’, the code runs on the user thread that did an Async.Run.) ‘let!’ lets go of a thread while the Async operation is at sea, and then picks up a thread from the ThreadPool when the operation returns. The (performance) advantage is less pressure against the ThreadPool (and of course the major user advantage is the simple programming model – a million times better than all that BeginFoo/EndFoo/callback stuff you otherwise write).

    See also http://cs.hubfs.net/forums/thread/8262.aspx

    • 0