This is an extract from a quite technical document. In addition to the problem of understanding the English constructs, you have second challenge in that certain terms have specialised technical meanings. Here we see process being used in a very particular way, as well as processing being used in a subtly different but related way.
In understanding this passage you need to identify the technical terms and establish their meaning in this particular document. You cannot do this simply by reading this one paragraph. We would hope that there would be a glossary for this particular document that would define the terms, however there may well not be one, so instead we at least need to look at a technical dictionary (for example), we cannot simply appeal to standard English usage.
So here you need to know what process, web server, request, concurrent and processing mean.
From my own knowledge of this field the Web Server is a particular process running on a computer, there will be many such processes running. The Web Server has responsibility to receive requests (typically from a Browser) and performs processing to satisfy those requests.
Here we come to the meaning of on behalf which can mean in the interest or aid of. So for each request some processing is done, that processing is on behalf of a single request.
The key idea is that the Web Server is satisfying multiple requests at the same time concurrently. And the issue being addressed is what happens is one request's processing effectively monopolises the Web Server for a period of time, in this case the other requests, concurrently being processed are stalled until the monopolising processing is finished.
Hence to understand this paragraph we need to get definitions of some technical terms but also need some quite detailed technical background information about multi-threaded concurrent processing.
The only slightly tricky English here is the on behalf, which becomes clear when we understand the relationship between a request and its processing.
First of all, could, good, and cook don't have /u:/, they have /ʊ/, a completely different vowel.
This is /ʊ/: https://en.wikipedia.org/wiki/Near-close_near-back_rounded_vowel
This is /u/: https://en.wikipedia.org/wiki/Close_back_rounded_vowel
Your cuckoo sentence is pronounced:
/haʊ mɛni kʊkuːz kʊd ə gʊd kʊk kʊk ɪf ə gʊd kʊk kʊd kʊk kʊkuːz/
Secondly, those pronunciation-exercising sentences are called tongue twisters. Tongue twisters are phrases contrived to be difficult to pronounce as you are exposed to it, such as the famous "She sells sea-shells on the sea-shore."
Now, your direct question: "Make a tongue-twister for /n/ and /l/", here's what P.E. Dant said in your comments:
Nine nimble nobles nibbled nuts, might help with /n/. You can find thousands of tongue-twister sites, with entries sort by letter. Here is a page with several which are intended to help with /l/. Try a Google search for "tongue twisters for /l/ and /n/".
What is "tongue to a sentence" of N & L sound?
The point of using tongue twisters for pronunciation exercises is to be contrived to be hard to pronounce so that you can improve on them, and consequently the sounds the twister contains. I think you can make up your own, as you've already done.
Best Answer
I had not heard this phrase before, but it apparently is used to describe a sentence that starts and ends with the same word. It is also called an epanalepsis. (Source)
It is not a bad thing. Wikipedia states that the structure of such a sentence makes one pay special attention to it, and I agree.
One of the examples on the Wikipedia page is a well-known phrase:
You will find such a structure only used in literary contexts, though. It is not something used in ordinary, everyday conversations.