Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Index compression |
Thu, Dec 7 2006 11:41 AM | Permanent Link |
"Jose Eduardo Helminsky" | Tim
I have some doubt about index compression: As a general rule or I use index compression in ALL indexes or I don´t use compression. My doubts: 1) The process of create the index will be slower with compression ? 2) The process of update the index (during a post or update) will be slower with compression ? 3) Browsing records will be slower using compression ? 4) As I told before, is it better use compression to ALL indexes or don´t use compression ? Eduardo |
Thu, Dec 7 2006 4:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Eduardo,
<< 1) The process of create the index will be slower with compression ? >> Normally, no - the compression will reduce the necessary I/O to the point that the additional CPU time required for the compression is less than the I/O time saved. This is all dependent upon using the guidelines here to properly choose the correct type of index compression: http://www.elevatesoft.com/dbisam4d5_index_compression.htm << 2) The process of update the index (during a post or update) will be slower with compression ? >> In terms of actual CPU time, yes. However, in aggregate you should be saving a lot more time in terms of I/O time required. << 3) Browsing records will be slower using compression ? >> Same as updating above - there is a trade-off. << 4) As I told before, is it better use compression to ALL indexes or don´t use compression ? >> It is best to use the guidelines I linked to above to set the index compression. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, September 20, 2024 at 05:39 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |