-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First of All , Thanks to all your help ;-) All the replies are good , and enlightened me.
Finally as i read more of the book , i found a good way to solve this problem. They use multiple queues , which has different CPU time for a slice. That's a good way as a statistics of running time. Shorter tasks will be available to execute , and finish earlier. - --------------------------------- | 7s CPU time per slice | // Queue 1 - --------------------------------- ==> if a process didn't finish , move it to next queue. - --------------------------------- | 14s per slice (maybe) | // Queue 2 - --------------------------------- ... And different queues owns different priority , of course. Thanks again for all of your experience ! - -- Best Regards, Aaron Lewis - PGP: 0x4A6D32A0 FingerPrint EA63 26B2 6C52 72EA A4A5 EB6B BDFE 35B0 4A6D 32A0 irc: A4r0n on freenode Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNikYACgkQvf41sEptMqDnVACguzyJFMSyurqW6RpQE3lay/g3 M2gAn1wOQ+pl0guyKQQD7lQe2SBCAq71 =lHeF -----END PGP SIGNATURE-----
