See post #7

Adq
Yes, it is slow. You see this rotating pointer? It is 2 seconds in your case.

 
Well you said you were getting 40-45 seconds...2 seconds seems pretty fast compared to that, and fast in absolute terms. I'm still curious why you need to clone 10 Breverbs...
 

If you disable "Clone Properties" while cloning you will not see it.

 
Of course not. If you don't clone properties, SONAR doesn't have to analyze the track you're cloning and load all the parameters that get copied along with the clip data - volume, pan, gain, name, track icon, track height, edit filter, track color, etc. The more tracks you have, the more time it takes for SONAR to wipe the default settings of the new tracks and replace them with the properties of the track you want to clone. 
 
If you don't clone properties, then the tracks are copied with default settings. As nothing needs to be changed, the process goes faster. This seems like a real non-issue to me...if you ask a program to do multiple things, it will take more time than if you don't ask a program to do multiple things.

Yeah, but you didn't compare it to cloning without "Clone Properties" checkmark.

Bristol_Jonesey
See post #7

Adq
Yeah, but you didn't compare it to cloning without "Clone Properties" checkmark.

Read post #22. SONAR has to do many more tasks if you Clone Properties, and doing more tasks takes more time. If you don't Clone Properties, SONAR doesn't have to do those tasks, which takes less time.

Anderton
Of course not. If you don't clone properties, SONAR doesn't have to analyze the track you're cloning and load all the parameters that get copied along with the clip data - volume, pan, gain, name, track icon, track height, edit filter, track color, etc. The more tracks you have, the more time it takes for SONAR to wipe the default settings of the new tracks and replace them with the properties of the track you want to clone. 
 
If you don't clone properties, then the tracks are copied with default settings. As nothing needs to be changed, the process goes faster. This seems like a real non-issue to me...if you ask a program to do multiple things, it will take more time than if you don't ask a program to do multiple things.

This not how programs work. If track without effects is cloning instantly, including properties. And track with effects but without properties is cloning instantly. Then track with effects and properties should be cloning instantlyб otherwise it is bug. In some cases it is 2 seconds, in some 10, in some it is minutes. And it is the same bug.

Anderton

Adq
Yeah, but you didn't compare it to cloning without "Clone Properties" checkmark.

Read post #22. SONAR has to do many more tasks if you Clone Properties, and doing more tasks takes more time. If you don't Clone Properties, SONAR doesn't have to do those tasks, which takes less time.

Yes, but no one of this tasks have any deal with effects.

Anderton
If track without effects is cloning instantly, including properties. 

 
That is not what I'm seeing. Although the tracks themselves appear almost instantly, it takes a while to populate the parameters.
 
Do this. Name a track without effects some distinctive name, like "Arf." Clone it 10 times without effects but with properties. The tracks appear almost instantly, but have names like Track 2, Track 3. The tracks aren't actually ready until the names like Track 2 etc. are replaced with the name "Arf." If there are lots of effects and you check effects, it will take longer. If you have lots of sends and check that too, it will add more time, although not as much.
 
What I'm seeing is the more elements you ask SONAR to clone, the more time it takes. The longest time to clone is if there are lot of effects and sends, and everything is checked. 

Ok, maybe I was not exactly right about instant cloning without effects, but

Anderton
Do this. Name a track without effects some distinctive name, like "Arf." Clone it 10 times without effects but with properties. The tracks appear almost instantly, but have names like Track 2, Track 3. The tracks aren't actually ready until the names like Track 2 etc. are replaced with the name "Arf."

This alone is already bug description. Cloning is slow - that is the bug. It is not because it does some hard work. It because it does some unnecessary work.

Anderton
What I'm seeing is the more elements you ask SONAR to clone, the more time it takes. The longest time to clone is if there are lot of effects and sends, and everything is checked. 

I can understand why you don't clearly see that it is the bug. In your case times are relatively fast. But if you do clone 10 or 20 repetitions without plug-ins, with 10 plug-ins on track but without properties, and finally with 10 plug-ins and with properties, the time in former case would be much more than sum of first two. That is what i see.
Why I do it? I wanted to benchmark Sonar CPU Performance, in it failed on the zero stage (cloning tracks).

As I said to Craig he should throttle his CPU 

Adq
But if you do clone 10 or 20 repetitions without plug-ins, with 10 plug-ins on track but without properties, and finally with 10 plug-ins and with properties, the time in former case would be much more than sum of first two. That is what i see.

Interesting, that's not at all what I see:
 
10 or 20 repetitions without plug-ins but with properties = fastest
10 plug-ins on track but without properties = almost as fast
10 plug-ins and with properties = clearly slower
 
Those are the kind of results I'd expect. I'm using an i7 on a laptop, though.