Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Tue, 31 May 2005 17:38:54 -0500,    group: microsoft.public.exchange2000.clustering        back       


Poor Performace    
Does anybody know of any diagnostic/performance tools that I can use on my 
Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
exchange database is about 100GB in size.  When a user clicks on a message 
in Outlook it can take 10-15 seconds to retrieve the message.  Sometimes we 
get the popup " retrieving data from Exchange server"  This occurs on all 
messages even ones without attachments.  I realize that it would do this 
with a large attachment but this happens when a blank message with the 
subject of HI.  I don't recall this type of latency when we were not 
clustered.  Any info you can provide would be greatly appreciated.

Regards,

Robby
date: Tue, 31 May 2005 17:38:54 -0500   author:   Robby Pollard

Re: Poor Performace    
Without knowing much about your environment, I would first look at the 
performance of your storage infrastructure (SAN, NAS, or DAS?). As long 
as your servers appear healthy and report low utilization of system 
recourses, look into these items:
* Download JetStress to test the performance of your storage solution in 
relation to database access.
* 100GB is pretty big for a single DB. Exchange should be able to handle 
it fine, but you may want to distribute the mailboxes evenly over a few 
databases to reduce the size of your databases.
* After a successful backup of the database and logs, use eseutil to 
scan and possibly defragment the database if necessary.



Robby Pollard wrote:
> Does anybody know of any diagnostic/performance tools that I can use on my 
> Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
> exchange database is about 100GB in size.  When a user clicks on a message 
> in Outlook it can take 10-15 seconds to retrieve the message.  Sometimes we 
> get the popup " retrieving data from Exchange server"  This occurs on all 
> messages even ones without attachments.  I realize that it would do this 
> with a large attachment but this happens when a blank message with the 
> subject of HI.  I don't recall this type of latency when we were not 
> clustered.  Any info you can provide would be greatly appreciated.
> 
> Regards,
> 
> Robby
> 
>
date: Tue, 31 May 2005 13:42:15 -1000   author:   Aran am

Re: Poor Performace    
Thanks for the info!  I have two Dell Power Edge Servers each with dual 
3.2Mhz procs and 6GB RAM.  For the storage unit it is a Dell Power Edge 221L 
Storage unit.  It ran fine with the 100GB DB before clustering on the same 
hardware.  I will split it out into a couple of DB's.  If you have any other 
thoughts please let me know.

Robby

-- 
WILLIAM POLLARD
"Aran" <Aran@newsgroup.nospam> wrote in message 
news:edCtipjZFHA.1384@TK2MSFTNGP09.phx.gbl...
> Without knowing much about your environment, I would first look at the 
> performance of your storage infrastructure (SAN, NAS, or DAS?). As long as 
> your servers appear healthy and report low utilization of system 
> recourses, look into these items:
> * Download JetStress to test the performance of your storage solution in 
> relation to database access.
> * 100GB is pretty big for a single DB. Exchange should be able to handle 
> it fine, but you may want to distribute the mailboxes evenly over a few 
> databases to reduce the size of your databases.
> * After a successful backup of the database and logs, use eseutil to scan 
> and possibly defragment the database if necessary.
>
>
>
> Robby Pollard wrote:
>> Does anybody know of any diagnostic/performance tools that I can use on 
>> my Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
>> exchange database is about 100GB in size.  When a user clicks on a 
>> message in Outlook it can take 10-15 seconds to retrieve the message. 
>> Sometimes we get the popup " retrieving data from Exchange server"  This 
>> occurs on all messages even ones without attachments.  I realize that it 
>> would do this with a large attachment but this happens when a blank 
>> message with the subject of HI.  I don't recall this type of latency when 
>> we were not clustered.  Any info you can provide would be greatly 
>> appreciated.
>>
>> Regards,
>>
>> Robby
>>
date: Tue, 31 May 2005 19:22:43 -0500   author:   Robby

Re: Poor Performace    
Here is part of the log.  Hope it helps.  What do i need to do to release 
the numbers?



5/31/2005 8:10:29 PM -- Environment validation results:
Detected JetstressUI version: 6.5.7529.0
Detected operating system: Microsoft Windows Server 2003 (5.2.3790.0)
Detected ESE.dll version: 6.5.7226.2
Detected ESEPERF.dll version: 6.5.7226.0
5/31/2005 8:10:29 PM -- Service MsExchangeSA is not found on the machine.
5/31/2005 8:10:29 PM -- Service IISAdmin is not found on the machine.
5/31/2005 8:10:29 PM -- Validating input parameters, it may take a few 
minutes...
5/31/2005 8:10:31 PM -- The total database size is 150MB which is too small 
compared to the hardware storage cache size. For the purpose of this test, 
you should increase the maximum number of mailboxes or mailbox size, in 
order to get an adequate database size. The recommended database size is 
512MB.
5/31/2005 8:10:34 PM -- There is not enough disk space on drive , the 
required space is 50 MB, and available space is 0 MB.
5/31/2005 8:10:37 PM -- Cleaning the log files created before test.
5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
5/31/2005 8:14:07 PM -- Inserting records: 16000 records have been inserted. 
Database creation process has completed 100%.
5/31/2005 8:14:07 PM -- Database creation has completed. The record size is 
1600 bytes, and the total database size created is 0.2 GB.
5/31/2005 8:14:07 PM -- Populate database...
5/31/2005 8:14:37 PM -- Database file copy progress:
Z:\EXCHSRVR\MDBDATA\Jetstress1.edb (42.01MB of 42.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress2.edb (42.01MB of 42.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress3.edb (42.01MB of 42.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress4.edb (42.01MB of 42.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress5.edb (42.01MB of 42.01MB copied),
Z:\Jetstress.edb.bak (42.01MB of 42.01MB copied).
5/31/2005 8:14:37 PM -- Cleaning the log files created before test.
5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
5/31/2005 8:14:38 PM -- Loading file JS_Config.xml...
5/31/2005 8:14:38 PM -- Instance Thread0: Jetstress parameters are: 1 64 90 
17 68 5
5/31/2005 8:14:38 PM -- Start Jetstress test...
5/31/2005 8:14:51 PM -- Loading performance counters...
5/31/2005 8:14:51 PM -- Start tuning process, this may take an hour 
depending on the testing environment...
5/31/2005 8:15:21 PM -- Disk latency slope of instance 1: is 
0.342003509853726
5/31/2005 8:17:21 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:17:21 PM -- Instance Thread0: the value for Actual Disk transfer 
is 182
5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk read latency 
is 6.75664275288582
5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk write 
latency is 89.1731688817342
5/31/2005 8:17:21 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log write size  is 
6352.83012746175
5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB write IO  is 
73.098850351572
5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB read IO  is 
109.073811292648
5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB IO  is 182
5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log IO  is 
26.6582250118256
5/31/2005 8:17:21 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
0
5/31/2005 8:17:21 PM -- Instance Thread0: Jetstress parameters are: 1,90, 
17, 67 ,4
5/31/2005 8:17:51 PM -- Disk latency slope of instance 1: is 
0.0129061816160032
5/31/2005 8:19:51 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:19:51 PM -- Instance Thread0: the value for Actual Disk transfer 
is 172
5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk read latency 
is 10.6541657229265
5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk write 
latency is 107.547055300077
5/31/2005 8:19:51 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log write size  is 
10797.7098765055
5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB write IO  is 
67.2169089794159
5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB read IO  is 
105.777247422934
5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB IO  is 172
5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log IO  is 
26.2392056375742
5/31/2005 8:19:51 PM -- Instance Thread0: Changed params are -1, 
0, -1, -1, -3
5/31/2005 8:19:51 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
17, 66 ,3
5/31/2005 8:20:21 PM -- Disk latency slope of instance 1: is 
0.00290580450114513
5/31/2005 8:22:22 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:22:22 PM -- Instance Thread0: the value for Actual Disk transfer 
is 171
5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk read latency 
is 7.27483408202728
5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk write 
latency is 136.129249064128
5/31/2005 8:22:22 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log write size  is 
7158.26638234456
5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB write IO  is 
68.210320409139
5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB read IO  is 
103.466706609726
5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB IO  is 171
5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log IO  is 
31.449728389581
5/31/2005 8:22:22 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
0
5/31/2005 8:22:22 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
17, 65 ,2
5/31/2005 8:22:52 PM -- Disk latency slope of instance 1: is 
0.0253865806252975
5/31/2005 8:24:52 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:24:52 PM -- Instance Thread0: the value for Actual Disk transfer 
is 180
5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk read latency 
is 5.5335195923845
5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk write 
latency is 165.439267158508
5/31/2005 8:24:52 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log write size  is 
4765.07565816243
5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB write IO  is 
69.2693589289983
5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB read IO  is 
111.260825872421
5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB IO  is 180
5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log IO  is 
34.3270712653796
5/31/2005 8:24:52 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
1
5/31/2005 8:24:52 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
17, 64 ,1
5/31/2005 8:25:22 PM -- Disk latency slope of instance 1: is 
0.0179765500430872
5/31/2005 8:27:22 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:27:22 PM -- Instance Thread0: the value for Actual Disk transfer 
is 178
5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk read latency 
is 5.90292643855015
5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk write 
latency is 196.523670768738
5/31/2005 8:27:22 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log write size  is 
7116.5622370402
5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB write IO  is 
69.0223689556122
5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB read IO  is 
109.135798168182
5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB IO  is 178
5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log IO  is 
30.5000422875086
5/31/2005 8:27:22 PM -- Instance Thread0: Changed params are -1, 0, -1, 0, 0
5/31/2005 8:27:22 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
17, 63 ,1
5/31/2005 8:27:52 PM -- Disk latency slope of instance 1: is 
0.349810401432862
5/31/2005 8:29:53 PM -- Instance Thread0: the value for Target Disk transfer 
is 1
5/31/2005 8:29:53 PM -- Instance Thread0: the value for Actual Disk transfer 
is 174
5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk read latency 
is 6.47243171110749
5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk write 
latency is 219.457436307271
5/31/2005 8:29:53 PM -- Instance Thread0: the write latency on the DB or Log 
drive is too high. The peak is more than 40ms.
5/31/2005 8:29:53 PM -- Instance Thread0: the value for Log write size  is 
6602.84921925863
5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB write IO  is 
66.0847864309947


-- 
WILLIAM POLLARD
"Robby"  wrote in message 
news:eNbvIAkZFHA.2996@TK2MSFTNGP10.phx.gbl...
> Thanks for the info!  I have two Dell Power Edge Servers each with dual 
> 3.2Mhz procs and 6GB RAM.  For the storage unit it is a Dell Power Edge 
> 221L Storage unit.  It ran fine with the 100GB DB before clustering on the 
> same hardware.  I will split it out into a couple of DB's.  If you have 
> any other thoughts please let me know.
>
> Robby
>
> -- 
> WILLIAM POLLARD
> "Aran" <Aran@newsgroup.nospam> wrote in message 
> news:edCtipjZFHA.1384@TK2MSFTNGP09.phx.gbl...
>> Without knowing much about your environment, I would first look at the 
>> performance of your storage infrastructure (SAN, NAS, or DAS?). As long 
>> as your servers appear healthy and report low utilization of system 
>> recourses, look into these items:
>> * Download JetStress to test the performance of your storage solution in 
>> relation to database access.
>> * 100GB is pretty big for a single DB. Exchange should be able to handle 
>> it fine, but you may want to distribute the mailboxes evenly over a few 
>> databases to reduce the size of your databases.
>> * After a successful backup of the database and logs, use eseutil to scan 
>> and possibly defragment the database if necessary.
>>
>>
>>
>> Robby Pollard wrote:
>>> Does anybody know of any diagnostic/performance tools that I can use on 
>>> my Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
>>> exchange database is about 100GB in size.  When a user clicks on a 
>>> message in Outlook it can take 10-15 seconds to retrieve the message. 
>>> Sometimes we get the popup " retrieving data from Exchange server"  This 
>>> occurs on all messages even ones without attachments.  I realize that it 
>>> would do this with a large attachment but this happens when a blank 
>>> message with the subject of HI.  I don't recall this type of latency 
>>> when we were not clustered.  Any info you can provide would be greatly 
>>> appreciated.
>>>
>>> Regards,
>>>
>>> Robby
>>>
>
date: Tue, 31 May 2005 20:52:49 -0500   author:   Robby

Re: Poor Performace    
Here are more of the results for today.  Any help is greatly appreciated.

Robby

6/1/2005 9:08:07 AM -- Environment validation results:
Detected JetstressUI version: 6.5.7529.0
Detected operating system: Microsoft Windows Server 2003 (5.2.3790.0)
Detected ESE.dll version: 6.5.7226.2
Detected ESEPERF.dll version: 6.5.7226.0
6/1/2005 9:08:07 AM -- Service MsExchangeSA is not found on the machine.
6/1/2005 9:08:07 AM -- Service IISAdmin is not found on the machine.
6/1/2005 9:08:07 AM -- Validating input parameters, it may take a few minutes...
6/1/2005 9:08:14 AM -- There is not enough disk space on drive , the required space is 2500 MB, and available space is 0 MB.
6/1/2005 9:08:15 AM -- Cleaning the log files created before test.
6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
6/1/2005 4:09:27 PM -- Inserting records: 782000 records have been inserted. Database creation process has completed 100%.
6/1/2005 4:09:28 PM -- Database creation has completed. The record size is 1600 bytes, and the total database size created is 7.5 GB.
6/1/2005 4:09:28 PM -- Populate database...
6/1/2005 4:34:46 PM -- Database file copy progress:
Z:\EXCHSRVR\MDBDATA\Jetstress1.edb (2,037.01MB of 2,037.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress2.edb (2,037.01MB of 2,037.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress3.edb (2,037.01MB of 2,037.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress4.edb (2,037.01MB of 2,037.01MB copied),
Z:\EXCHSRVR\MDBDATA\Jetstress5.edb (2,037.01MB of 2,037.01MB copied),
Z:\Jetstress.edb.bak (2,037.01MB of 2,037.01MB copied).
6/1/2005 4:34:47 PM -- Cleaning the log files created before test.
6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
6/1/2005 4:34:58 PM -- Loading file JS_Config.xml...
6/1/2005 4:35:02 PM -- Instance Thread0: Jetstress parameters are: 1 64 90 17 68 5 
6/1/2005 4:35:02 PM -- Start Jetstress test...
6/1/2005 4:35:17 PM -- Loading performance counters...
6/1/2005 4:35:19 PM -- Start tuning process, this may take an hour depending on the testing environment...
6/1/2005 4:35:58 PM -- Disk latency slope of instance 1: is 0.196545584560357
6/1/2005 4:37:58 PM -- Instance Thread0: the value for Target Disk transfer is 7.5
6/1/2005 4:37:58 PM -- Instance Thread0: the value for Actual Disk transfer is 94
6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB Disk read latency is 106.824300980568
6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB Disk write latency is 397.562175432841
6/1/2005 4:37:58 PM -- Instance Thread0: the write latency on the DB or Log drive is too high. The peak is more than 40ms.
6/1/2005 4:37:58 PM -- Instance Thread0: the value for Log write size is 6955.10294138591
6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB write IO is 22.7337780624628
6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB read IO is 72.1085324292382
6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB IO is 94
6/1/2005 4:37:58 PM -- Instance Thread0: the value for Log IO is 8.88659390558799
6/1/2005 4:37:58 PM -- Instance Thread0: Changed params are -1, 3, -2, -1, 0
6/1/2005 4:37:58 PM -- Instance Thread0: Jetstress parameters are: 1,90, 20, 66 ,4 
6/1/2005 4:38:28 PM -- Disk latency slope of instance 1: is 0.592564096042537
6/1/2005 4:38:58 PM -- Disk latency slope of instance 1: is 4.40317796378444

"Robby"  wrote in message news:epdnfykZFHA.2796@TK2MSFTNGP10.phx.gbl...
> Here is part of the log.  Hope it helps.  What do i need to do to release 
> the numbers?
> 
> 
> 
> 5/31/2005 8:10:29 PM -- Environment validation results:
> Detected JetstressUI version: 6.5.7529.0
> Detected operating system: Microsoft Windows Server 2003 (5.2.3790.0)
> Detected ESE.dll version: 6.5.7226.2
> Detected ESEPERF.dll version: 6.5.7226.0
> 5/31/2005 8:10:29 PM -- Service MsExchangeSA is not found on the machine.
> 5/31/2005 8:10:29 PM -- Service IISAdmin is not found on the machine.
> 5/31/2005 8:10:29 PM -- Validating input parameters, it may take a few > minutes...
> 5/31/2005 8:10:31 PM -- The total database size is 150MB which is too small 
> compared to the hardware storage cache size. For the purpose of this test, 
> you should increase the maximum number of mailboxes or mailbox size, in 
> order to get an adequate database size. The recommended database size is 
> 512MB.
> 5/31/2005 8:10:34 PM -- There is not enough disk space on drive , the 
> required space is 50 MB, and available space is 0 MB.
> 5/31/2005 8:10:37 PM -- Cleaning the log files created before test.
> 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
> 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
> 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
> 5/31/2005 8:14:07 PM -- Inserting records: 16000 records have been inserted. 
> Database creation process has completed 100%.
> 5/31/2005 8:14:07 PM -- Database creation has completed. The record size is 
> 1600 bytes, and the total database size created is 0.2 GB.
> 5/31/2005 8:14:07 PM -- Populate database...
> 5/31/2005 8:14:37 PM -- Database file copy progress:
> Z:\EXCHSRVR\MDBDATA\Jetstress1.edb (42.01MB of 42.01MB copied),
> Z:\EXCHSRVR\MDBDATA\Jetstress2.edb (42.01MB of 42.01MB copied),
> Z:\EXCHSRVR\MDBDATA\Jetstress3.edb (42.01MB of 42.01MB copied),
> Z:\EXCHSRVR\MDBDATA\Jetstress4.edb (42.01MB of 42.01MB copied),
> Z:\EXCHSRVR\MDBDATA\Jetstress5.edb (42.01MB of 42.01MB copied),
> Z:\Jetstress.edb.bak (42.01MB of 42.01MB copied).
> 5/31/2005 8:14:37 PM -- Cleaning the log files created before test.
> 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
> 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
> 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
> 5/31/2005 8:14:38 PM -- Loading file JS_Config.xml...
> 5/31/2005 8:14:38 PM -- Instance Thread0: Jetstress parameters are: 1 64 90 
> 17 68 5
> 5/31/2005 8:14:38 PM -- Start Jetstress test...
> 5/31/2005 8:14:51 PM -- Loading performance counters...
> 5/31/2005 8:14:51 PM -- Start tuning process, this may take an hour 
> depending on the testing environment...
> 5/31/2005 8:15:21 PM -- Disk latency slope of instance 1: is 
> 0.342003509853726
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 182
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk read latency 
> is 6.75664275288582
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk write 
> latency is 89.1731688817342
> 5/31/2005 8:17:21 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log write size  is 
> 6352.83012746175
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB write IO  is 
> 73.098850351572
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB read IO  is > 109.073811292648
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB IO  is 182
> 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log IO  is 
> 26.6582250118256
> 5/31/2005 8:17:21 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
> 0
> 5/31/2005 8:17:21 PM -- Instance Thread0: Jetstress parameters are: 1,90, 
> 17, 67 ,4
> 5/31/2005 8:17:51 PM -- Disk latency slope of instance 1: is 
> 0.0129061816160032
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 172
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk read latency 
> is 10.6541657229265
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk write 
> latency is 107.547055300077
> 5/31/2005 8:19:51 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log write size  is 
> 10797.7098765055
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB write IO  is 
> 67.2169089794159
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB read IO  is > 105.777247422934
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB IO  is 172
> 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log IO  is 
> 26.2392056375742
> 5/31/2005 8:19:51 PM -- Instance Thread0: Changed params are -1, 
> 0, -1, -1, -3
> 5/31/2005 8:19:51 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
> 17, 66 ,3
> 5/31/2005 8:20:21 PM -- Disk latency slope of instance 1: is 
> 0.00290580450114513
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 171
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk read latency 
> is 7.27483408202728
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk write 
> latency is 136.129249064128
> 5/31/2005 8:22:22 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log write size  is 
> 7158.26638234456
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB write IO  is 
> 68.210320409139
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB read IO  is > 103.466706609726
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB IO  is 171
> 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log IO  is 
> 31.449728389581
> 5/31/2005 8:22:22 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
> 0
> 5/31/2005 8:22:22 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
> 17, 65 ,2
> 5/31/2005 8:22:52 PM -- Disk latency slope of instance 1: is 
> 0.0253865806252975
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 180
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk read latency 
> is 5.5335195923845
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk write 
> latency is 165.439267158508
> 5/31/2005 8:24:52 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log write size  is 
> 4765.07565816243
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB write IO  is 
> 69.2693589289983
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB read IO  is > 111.260825872421
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB IO  is 180
> 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log IO  is 
> 34.3270712653796
> 5/31/2005 8:24:52 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
> 1
> 5/31/2005 8:24:52 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
> 17, 64 ,1
> 5/31/2005 8:25:22 PM -- Disk latency slope of instance 1: is 
> 0.0179765500430872
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 178
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk read latency 
> is 5.90292643855015
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk write 
> latency is 196.523670768738
> 5/31/2005 8:27:22 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log write size  is 
> 7116.5622370402
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB write IO  is 
> 69.0223689556122
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB read IO  is > 109.135798168182
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB IO  is 178
> 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log IO  is 
> 30.5000422875086
> 5/31/2005 8:27:22 PM -- Instance Thread0: Changed params are -1, 0, -1, 0, 0
> 5/31/2005 8:27:22 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
> 17, 63 ,1
> 5/31/2005 8:27:52 PM -- Disk latency slope of instance 1: is 
> 0.349810401432862
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Target Disk transfer 
> is 1
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Actual Disk transfer 
> is 174
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk read latency 
> is 6.47243171110749
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk write 
> latency is 219.457436307271
> 5/31/2005 8:29:53 PM -- Instance Thread0: the write latency on the DB or Log 
> drive is too high. The peak is more than 40ms.
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Log write size  is 
> 6602.84921925863
> 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB write IO  is 
> 66.0847864309947
> 
> 
> -- 
> WILLIAM POLLARD
> "Robby"  wrote in message 
> news:eNbvIAkZFHA.2996@TK2MSFTNGP10.phx.gbl...
>> Thanks for the info!  I have two Dell Power Edge Servers each with dual 
>> 3.2Mhz procs and 6GB RAM.  For the storage unit it is a Dell Power Edge 
>> 221L Storage unit.  It ran fine with the 100GB DB before clustering on the 
>> same hardware.  I will split it out into a couple of DB's.  If you have 
>> any other thoughts please let me know.
>>
>> Robby
>>
>> -- 
>> WILLIAM POLLARD
>> "Aran" <Aran@newsgroup.nospam> wrote in message 
>> news:edCtipjZFHA.1384@TK2MSFTNGP09.phx.gbl...
>>> Without knowing much about your environment, I would first look at the 
>>> performance of your storage infrastructure (SAN, NAS, or DAS?). As long 
>>> as your servers appear healthy and report low utilization of system 
>>> recourses, look into these items:
>>> * Download JetStress to test the performance of your storage solution in 
>>> relation to database access.
>>> * 100GB is pretty big for a single DB. Exchange should be able to handle 
>>> it fine, but you may want to distribute the mailboxes evenly over a few 
>>> databases to reduce the size of your databases.
>>> * After a successful backup of the database and logs, use eseutil to scan 
>>> and possibly defragment the database if necessary.
>>>
>>>
>>>
>>> Robby Pollard wrote:
>>>> Does anybody know of any diagnostic/performance tools that I can use on 
>>>> my Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
>>>> exchange database is about 100GB in size.  When a user clicks on a 
>>>> message in Outlook it can take 10-15 seconds to retrieve the message. 
>>>> Sometimes we get the popup " retrieving data from Exchange server"  This 
>>>> occurs on all messages even ones without attachments.  I realize that it 
>>>> would do this with a large attachment but this happens when a blank >>>> message with the subject of HI.  I don't recall this type of latency 
>>>> when we were not clustered.  Any info you can provide would be greatly 
>>>> appreciated.
>>>>
>>>> Regards,
>>>>
>>>> Robby
>>>>
>> 
> 
>
date: Wed, 1 Jun 2005 16:44:46 -0500   author:   Robby Pollard

Re: Poor Performace    
Robby:

Can you tell us a little more about the configuration of your physical disks, whether users are cached mode or not, whether or not you have a BES server and how many BlackBerry users exist, the current size of your disks, how the Disks are configured (if it's on a SAN note whether or not it shares application space), RAID card and cache, etc?  

With 180 users you should not have the latency problems that you appear to be experiencing.  

My guess is that 
1) You may have some disk issues and the storage may not be optimized (then again...you have just 180 users)
2)  Something else is overloading your disks
3)  It may be possible that someone or something is using your server as a relay www.amset.info/exchange  has good information on determining if this is happening.
4)  Your file level anti-virus may be misconfigured.  This is a link for info on Symantec (look at the question and then scroll down to the bottom):
http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21300420.html
5)  Your Exchange anti-virus may be misconfigured.  Here is a link on Symantec Mail Security....but I like Sybari and Trend, too!
http://bobchristian.blogspot.com/2005/02/symantec-mail-security-settings.html

6)  Maintenance may still be running on your databases.
7)  Your backup software may be causing an issue.

Bob

"Robby Pollard"  wrote in message news:OoJQcLvZFHA.1384@TK2MSFTNGP09.phx.gbl...
  Here are more of the results for today.  Any help is greatly appreciated.

  Robby

  6/1/2005 9:08:07 AM -- Environment validation results:
  Detected JetstressUI version: 6.5.7529.0
  Detected operating system: Microsoft Windows Server 2003 (5.2.3790.0)
  Detected ESE.dll version: 6.5.7226.2
  Detected ESEPERF.dll version: 6.5.7226.0
  6/1/2005 9:08:07 AM -- Service MsExchangeSA is not found on the machine.
  6/1/2005 9:08:07 AM -- Service IISAdmin is not found on the machine.
  6/1/2005 9:08:07 AM -- Validating input parameters, it may take a few minutes...
  6/1/2005 9:08:14 AM -- There is not enough disk space on drive , the required space is 2500 MB, and available space is 0 MB.
  6/1/2005 9:08:15 AM -- Cleaning the log files created before test.
  6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
  6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
  6/1/2005 9:08:15 AM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
  6/1/2005 4:09:27 PM -- Inserting records: 782000 records have been inserted. Database creation process has completed 100%.
  6/1/2005 4:09:28 PM -- Database creation has completed. The record size is 1600 bytes, and the total database size created is 7.5 GB.
  6/1/2005 4:09:28 PM -- Populate database...
  6/1/2005 4:34:46 PM -- Database file copy progress:
  Z:\EXCHSRVR\MDBDATA\Jetstress1.edb (2,037.01MB of 2,037.01MB copied),
  Z:\EXCHSRVR\MDBDATA\Jetstress2.edb (2,037.01MB of 2,037.01MB copied),
  Z:\EXCHSRVR\MDBDATA\Jetstress3.edb (2,037.01MB of 2,037.01MB copied),
  Z:\EXCHSRVR\MDBDATA\Jetstress4.edb (2,037.01MB of 2,037.01MB copied),
  Z:\EXCHSRVR\MDBDATA\Jetstress5.edb (2,037.01MB of 2,037.01MB copied),
  Z:\Jetstress.edb.bak (2,037.01MB of 2,037.01MB copied).
  6/1/2005 4:34:47 PM -- Cleaning the log files created before test.
  6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
  6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
  6/1/2005 4:34:48 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
  6/1/2005 4:34:58 PM -- Loading file JS_Config.xml...
  6/1/2005 4:35:02 PM -- Instance Thread0: Jetstress parameters are: 1 64 90 17 68 5 
  6/1/2005 4:35:02 PM -- Start Jetstress test...
  6/1/2005 4:35:17 PM -- Loading performance counters...
  6/1/2005 4:35:19 PM -- Start tuning process, this may take an hour depending on the testing environment...
  6/1/2005 4:35:58 PM -- Disk latency slope of instance 1: is 0.196545584560357
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for Target Disk transfer is 7.5
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for Actual Disk transfer is 94
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB Disk read latency is 106.824300980568
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB Disk write latency is 397.562175432841
  6/1/2005 4:37:58 PM -- Instance Thread0: the write latency on the DB or Log drive is too high. The peak is more than 40ms.
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for Log write size is 6955.10294138591
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB write IO is 22.7337780624628
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB read IO is 72.1085324292382
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for DB IO is 94
  6/1/2005 4:37:58 PM -- Instance Thread0: the value for Log IO is 8.88659390558799
  6/1/2005 4:37:58 PM -- Instance Thread0: Changed params are -1, 3, -2, -1, 0
  6/1/2005 4:37:58 PM -- Instance Thread0: Jetstress parameters are: 1,90, 20, 66 ,4 
  6/1/2005 4:38:28 PM -- Disk latency slope of instance 1: is 0.592564096042537
  6/1/2005 4:38:58 PM -- Disk latency slope of instance 1: is 4.40317796378444

  "Robby"  wrote in message news:epdnfykZFHA.2796@TK2MSFTNGP10.phx.gbl...
  > Here is part of the log.  Hope it helps.  What do i need to do to release 
  > the numbers?
  > 
  > 
  > 
  > 5/31/2005 8:10:29 PM -- Environment validation results:
  > Detected JetstressUI version: 6.5.7529.0
  > Detected operating system: Microsoft Windows Server 2003 (5.2.3790.0)
  > Detected ESE.dll version: 6.5.7226.2
  > Detected ESEPERF.dll version: 6.5.7226.0
  > 5/31/2005 8:10:29 PM -- Service MsExchangeSA is not found on the machine.
  > 5/31/2005 8:10:29 PM -- Service IISAdmin is not found on the machine.
  > 5/31/2005 8:10:29 PM -- Validating input parameters, it may take a few 
  > minutes...
  > 5/31/2005 8:10:31 PM -- The total database size is 150MB which is too small 
  > compared to the hardware storage cache size. For the purpose of this test, 
  > you should increase the maximum number of mailboxes or mailbox size, in 
  > order to get an adequate database size. The recommended database size is 
  > 512MB.
  > 5/31/2005 8:10:34 PM -- There is not enough disk space on drive , the 
  > required space is 50 MB, and available space is 0 MB.
  > 5/31/2005 8:10:37 PM -- Cleaning the log files created before test.
  > 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
  > 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
  > 5/31/2005 8:10:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
  > 5/31/2005 8:14:07 PM -- Inserting records: 16000 records have been inserted. 
  > Database creation process has completed 100%.
  > 5/31/2005 8:14:07 PM -- Database creation has completed. The record size is 
  > 1600 bytes, and the total database size created is 0.2 GB.
  > 5/31/2005 8:14:07 PM -- Populate database...
  > 5/31/2005 8:14:37 PM -- Database file copy progress:
  > Z:\EXCHSRVR\MDBDATA\Jetstress1.edb (42.01MB of 42.01MB copied),
  > Z:\EXCHSRVR\MDBDATA\Jetstress2.edb (42.01MB of 42.01MB copied),
  > Z:\EXCHSRVR\MDBDATA\Jetstress3.edb (42.01MB of 42.01MB copied),
  > Z:\EXCHSRVR\MDBDATA\Jetstress4.edb (42.01MB of 42.01MB copied),
  > Z:\EXCHSRVR\MDBDATA\Jetstress5.edb (42.01MB of 42.01MB copied),
  > Z:\Jetstress.edb.bak (42.01MB of 42.01MB copied).
  > 5/31/2005 8:14:37 PM -- Cleaning the log files created before test.
  > 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\edb.log...
  > 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res1.log...
  > 5/31/2005 8:14:37 PM -- Delete file Z:\EXCHSRVR\MDBDATA\res2.log...
  > 5/31/2005 8:14:38 PM -- Loading file JS_Config.xml...
  > 5/31/2005 8:14:38 PM -- Instance Thread0: Jetstress parameters are: 1 64 90 
  > 17 68 5
  > 5/31/2005 8:14:38 PM -- Start Jetstress test...
  > 5/31/2005 8:14:51 PM -- Loading performance counters...
  > 5/31/2005 8:14:51 PM -- Start tuning process, this may take an hour 
  > depending on the testing environment...
  > 5/31/2005 8:15:21 PM -- Disk latency slope of instance 1: is 
  > 0.342003509853726
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 182
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 6.75664275288582
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 89.1731688817342
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log write size  is 
  > 6352.83012746175
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB write IO  is 
  > 73.098850351572
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB read IO  is 
  > 109.073811292648
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for DB IO  is 182
  > 5/31/2005 8:17:21 PM -- Instance Thread0: the value for Log IO  is 
  > 26.6582250118256
  > 5/31/2005 8:17:21 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
  > 0
  > 5/31/2005 8:17:21 PM -- Instance Thread0: Jetstress parameters are: 1,90, 
  > 17, 67 ,4
  > 5/31/2005 8:17:51 PM -- Disk latency slope of instance 1: is 
  > 0.0129061816160032
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 172
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 10.6541657229265
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 107.547055300077
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log write size  is 
  > 10797.7098765055
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB write IO  is 
  > 67.2169089794159
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB read IO  is 
  > 105.777247422934
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for DB IO  is 172
  > 5/31/2005 8:19:51 PM -- Instance Thread0: the value for Log IO  is 
  > 26.2392056375742
  > 5/31/2005 8:19:51 PM -- Instance Thread0: Changed params are -1, 
  > 0, -1, -1, -3
  > 5/31/2005 8:19:51 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
  > 17, 66 ,3
  > 5/31/2005 8:20:21 PM -- Disk latency slope of instance 1: is 
  > 0.00290580450114513
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 171
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 7.27483408202728
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 136.129249064128
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log write size  is 
  > 7158.26638234456
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB write IO  is 
  > 68.210320409139
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB read IO  is 
  > 103.466706609726
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for DB IO  is 171
  > 5/31/2005 8:22:22 PM -- Instance Thread0: the value for Log IO  is 
  > 31.449728389581
  > 5/31/2005 8:22:22 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
  > 0
  > 5/31/2005 8:22:22 PM -- Instance Thread0: Jetstress parameters are: 1,87, 
  > 17, 65 ,2
  > 5/31/2005 8:22:52 PM -- Disk latency slope of instance 1: is 
  > 0.0253865806252975
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 180
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 5.5335195923845
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 165.439267158508
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log write size  is 
  > 4765.07565816243
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB write IO  is 
  > 69.2693589289983
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB read IO  is 
  > 111.260825872421
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for DB IO  is 180
  > 5/31/2005 8:24:52 PM -- Instance Thread0: the value for Log IO  is 
  > 34.3270712653796
  > 5/31/2005 8:24:52 PM -- Instance Thread0: Changed params are -1, 0, -1, -1, 
  > 1
  > 5/31/2005 8:24:52 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
  > 17, 64 ,1
  > 5/31/2005 8:25:22 PM -- Disk latency slope of instance 1: is 
  > 0.0179765500430872
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 178
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 5.90292643855015
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 196.523670768738
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log write size  is 
  > 7116.5622370402
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB write IO  is 
  > 69.0223689556122
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB read IO  is 
  > 109.135798168182
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for DB IO  is 178
  > 5/31/2005 8:27:22 PM -- Instance Thread0: the value for Log IO  is 
  > 30.5000422875086
  > 5/31/2005 8:27:22 PM -- Instance Thread0: Changed params are -1, 0, -1, 0, 0
  > 5/31/2005 8:27:22 PM -- Instance Thread0: Jetstress parameters are: 1,88, 
  > 17, 63 ,1
  > 5/31/2005 8:27:52 PM -- Disk latency slope of instance 1: is 
  > 0.349810401432862
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Target Disk transfer 
  > is 1
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Actual Disk transfer 
  > is 174
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk read latency 
  > is 6.47243171110749
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB Disk write 
  > latency is 219.457436307271
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the write latency on the DB or Log 
  > drive is too high. The peak is more than 40ms.
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for Log write size  is 
  > 6602.84921925863
  > 5/31/2005 8:29:53 PM -- Instance Thread0: the value for DB write IO  is 
  > 66.0847864309947
  > 
  > 
  > -- 
  > WILLIAM POLLARD
  > "Robby"  wrote in message 
  > news:eNbvIAkZFHA.2996@TK2MSFTNGP10.phx.gbl...
  >> Thanks for the info!  I have two Dell Power Edge Servers each with dual 
  >> 3.2Mhz procs and 6GB RAM.  For the storage unit it is a Dell Power Edge 
  >> 221L Storage unit.  It ran fine with the 100GB DB before clustering on the 
  >> same hardware.  I will split it out into a couple of DB's.  If you have 
  >> any other thoughts please let me know.
  >>
  >> Robby
  >>
  >> -- 
  >> WILLIAM POLLARD
  >> "Aran" <Aran@newsgroup.nospam> wrote in message 
  >> news:edCtipjZFHA.1384@TK2MSFTNGP09.phx.gbl...
  >>> Without knowing much about your environment, I would first look at the 
  >>> performance of your storage infrastructure (SAN, NAS, or DAS?). As long 
  >>> as your servers appear healthy and report low utilization of system 
  >>> recourses, look into these items:
  >>> * Download JetStress to test the performance of your storage solution in 
  >>> relation to database access.
  >>> * 100GB is pretty big for a single DB. Exchange should be able to handle 
  >>> it fine, but you may want to distribute the mailboxes evenly over a few 
  >>> databases to reduce the size of your databases.
  >>> * After a successful backup of the database and logs, use eseutil to scan 
  >>> and possibly defragment the database if necessary.
  >>>
  >>>
  >>>
  >>> Robby Pollard wrote:
  >>>> Does anybody know of any diagnostic/performance tools that I can use on 
  >>>> my Clustered Exchange 2003 servers?  I am a shop of about 180 users.  My 
  >>>> exchange database is about 100GB in size.  When a user clicks on a 
  >>>> message in Outlook it can take 10-15 seconds to retrieve the message. 
  >>>> Sometimes we get the popup " retrieving data from Exchange server"  This 
  >>>> occurs on all messages even ones without attachments.  I realize that it 
  >>>> would do this with a large attachment but this happens when a blank 
  >>>> message with the subject of HI.  I don't recall this type of latency 
  >>>> when we were not clustered.  Any info you can provide would be greatly 
  >>>> appreciated.
  >>>>
  >>>> Regards,
  >>>>
  >>>> Robby
  >>>>
  >> 
  > 
  >
date: Fri, 10 Jun 2005 18:42:16 -0400   author:   Bob Christian

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us