Some Hashed File questions
Posted: Mon Apr 23, 2007 3:18 pm
Hi,
We are using the Hashed Files for doing the lookup. We just like to get certain informations clarified on this.
1) Does Hashed files have good performance only till the number of records that are loaded into it is less? We would have around 5,000 to 10,000 records as of now that needs to be loaded into the Hashed file. Would the performance slowly do down as the number of records slowly increments as days progress?
2) We specify the Read and Write cache size for Hashed files as default 128 MB in DS Administrator. Does it mean that this is the amount of data that it can hold in memory at a point in time?
3) Where does Hashed file put the data into cache and when does it put the data in the disk? Does it hold the data in cache to the maximum as specified in cache size and puts the remaining in the disk?
Thanks.
We are using the Hashed Files for doing the lookup. We just like to get certain informations clarified on this.
1) Does Hashed files have good performance only till the number of records that are loaded into it is less? We would have around 5,000 to 10,000 records as of now that needs to be loaded into the Hashed file. Would the performance slowly do down as the number of records slowly increments as days progress?
2) We specify the Read and Write cache size for Hashed files as default 128 MB in DS Administrator. Does it mean that this is the amount of data that it can hold in memory at a point in time?
3) Where does Hashed file put the data into cache and when does it put the data in the disk? Does it hold the data in cache to the maximum as specified in cache size and puts the remaining in the disk?
Thanks.