Hello Folks, I ran the Jetstress 2007 with 64 thread counts (per storage group) with suppress tuning on 8 SGs (8DB for 8LUNs, 8 Logs for 1 LUN), but the result shows that it ran with 50 thread counts although it shows the read latency < 10ms (low resources usage) I have no clue why it changed the number of thread count. Would you tell me why it's happened and no way to test with 64 threads counts? Thank you, swpark

64 is a very large thread count. When running Jetstress, the thread count isn't really of much importance. You use that number to tune the number of IOPS Jetstress throws at the server. You should be monitoring the disk IOPS counters to be sure that you're getting the numbers you want in the test, and not depending on Jetstress's figures. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "swpark" wrote in message news:c5ad1f3e-509e-40e5-abeb-a7f7fbfa3d31... Hello Folks, I ran the Jetstress 2007 with 64 thread counts (per storage group) with suppress tuning on 8 SGs (8DB for 8LUNs, 8 Logs for 1 LUN), but the result shows that it ran with 50 thread counts although it shows the read latency < 10ms (low resources usage) I have no clue why it changed the number of thread count. Would you tell me why it's happened and no way to test with 64 threads counts? Thank you, swparkEd Crowley MVP "There are seldom good technological solutions to behavioral problems."