I'm looking for a part-time remote job.

Hire me

I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).

Follow me:

Improvement #1988


Added by Andriy Lesyuk over 12 years ago.

Target version:
Start date:
26 Feb 2012
Due date:
% Done:



Currently Orangutan works in a single thread...

There are three levels of service performance in development: The first is single thread (obsolete style)... It is believed to be slow because the process works on single task and cannot process other requests at the time! Next and cooler level (normal nowadays) is multi-threaded... It’s what a normal server-side application should use!.. And the third and the coolest is... single thread (Yeah! I also find this funny!). It’s also the most advanced. It’s when an application is smart enough to delay some less important work to process more important work e.g. new requests...

Not sure how multi-threading can be enabled in Orangutan... But it should be at least some mix of the second and the third methods! Right now most tasks are small enough and there is not a big delay if Orangutan processes other person’s request (Well... It’s like a human who can’t speak to several humans at a time)!.. But in future things can change!..

Also available in: Atom PDF

Terms of use | Privacy policy