>>>jbb creates threads at the start of each warehouse run, and then lets them terminate at the end of the warehous run. Warehouse runs are ramped up from 1 to 2xCPU count threads, with 30/240s runtime per iteration for warmup/scoring respectively. See the jbb docs on http://www.spec.org
>>>
>>>for more detail.
>>
>>I really tought JBB was creating one thread for each "business operation" (a "client
>>request"?), not a few long running threads, hum... How scores would be affected if that was the case?
>
>That would definitely change the profile. Threads are >expensive to set up and tear
>down, so this is not a common pattern in Java apps.

Henrik,

What is the cost of setting up a Java thread? I'm assuming you measure it in either:
1. Cycles
2. Wallclock time
3. Instructions

What about the cost of destroying a thread? I'm not asking for JRockit specific numbers, but good general ranges.

David