always handle files using queues... ideas
Posted: 2006-11-24, 13:41 UTC
TC could always handle files using queues (that are running in separate threads). If I noticed well, there is always only one queue. When I perform extensive file operations, I would appreciate some or basic rules, that would drive the situation and made the work more effective. For example(!!!):
- IF copying(/moving/packing/unpacking/deletion/MD5 generating/ftp) between the same media... where another operation is already in progress THEN put the new file job into the same queue.
- Otherwise create the new queue.
(This means, that jobs to same media will always run in series and to different paralely.)
Maybe this particular way is not the best one, but currently there are definitely things to optimize. (threads, queues, etc.)
- IF copying(/moving/packing/unpacking/deletion/MD5 generating/ftp) between the same media... where another operation is already in progress THEN put the new file job into the same queue.
- Otherwise create the new queue.
(This means, that jobs to same media will always run in series and to different paralely.)
Maybe this particular way is not the best one, but currently there are definitely things to optimize. (threads, queues, etc.)