in 2.0, we switched to sqlite from derby for database. since sqlite does not have transaction logging (only redo logging), it's more sensitive to slow i/o.
one experiment you can try is to turn on sqlite debug logging, see how long does it take to do one transaction.
in your zd user data directory, you should find this file:
conf\log4j.properties
add this line to the end of the file and restart zd service:
log4j.logger.zimbra.sqltrace=DEBUG
you will see more log written to log\zdesktop.log. feel free to post them here if you are not sure how to interpret sql tracing.
Quote:
Originally Posted by kevindods Yes, guess so, but the difference was almost negligible when using ZD1 and the disks are SATA and SSD. 2-3hrs vs 2+days seems a little extreme for around 3GB
3GB in 48hrs is a little over 128Kb/s That would be a seriously slow drive even on SSD! ;-) |