@@ -1,10 +1,17 @@
1−-- | In a multithreaded environment, running actions on a regularly scheduled background thread can dramatically improve performance.
2−-- For example, web servers need to return the current time with each HTTP response.
3−-- For a high-volume server, it's much faster for a dedicated thread to run every second, and write the current time to a shared 'IORef', than it is for each request to make its own call to 'getCurrentTime'.
1+-- | In a multithreaded environment, running actions on a regularly scheduled
2+-- background thread can dramatically improve performance.
3+-- For example, web servers need to return the current time with each HTTP response.
4+-- For a high-volume server, it's much faster for a dedicated thread to run every
5+-- second, and write the current time to a shared 'IORef', than it is for each
6+-- request to make its own call to 'getCurrentTime'.
47--
5−-- But for a low-volume server, whose request frequency is less than once per second, that approach will result in /more/ calls to 'getCurrentTime' than necessary, and worse, kills idle GC.
8+-- But for a low-volume server, whose request frequency is less than once per
9+-- second, that approach will result in /more/ calls to 'getCurrentTime' than
10+-- necessary, and worse, kills idle GC.
611--
7−-- This library solves that problem by allowing you to define actions which will either be performed by a dedicated thread, or, in times of low volume, will be executed by the calling thread.
12+-- This library solves that problem by allowing you to define actions which will
13+-- either be performed by a dedicated thread, or, in times of low volume, will
14+-- be executed by the calling thread.
815--
916-- Example usage:
1017--