From Lazarus wiki
Revision as of 21:55, 26 July 2014 by Chronos (talk | contribs)


There are some situations where applications needs to execute a lots of asynchronous concurrent operations. OS-level threads could be used for this purpose but application can create only limited count of threads. In matter of CPU utilization there are no significant performance gain if more threads is created then physical cores CPU have. In fact threads could be used for parallel processing on multicore CPU and for writing more readable code. OS-level thread should be used mainly used for parallelism and better CPU utilization. If programmer needs to write code which will be called asynchronously than OS-level threads are rather expensive in perspective of system resource.

CPU context switching methods

  • Cooperative (use of explicit Yield call)
  • Preemptive (periodic timer based)
  • Combined


  • Unlimited number of instances (limited by available memory)
  • Fast switching, creation, destruction
  • Automatic thread pool management by physical CPU core count
  • Ability to run in main loop only (without TThread instances)
  • Provide own synchronization tools (Yield, Sleep, CriticalSection, Semaphore, Mutex, WaitForMultipleObjects, Queues, Synchronize, ...)
  • Priority control
  • Support for view list of all microthreads


  • MicroThreading - Lazarus package, functional yet not finished, not multi-platform, need patching FPC

External links