G
gus
Guest
another possibility is that when you rebuilt indexes after the load, there was no free space in the indexes. that is good for reading the loaded data but for some period after load, adding new records will cause index block splits since there is no room for new index entries. this causes a temporary performance degradation since every index insert requires allocating a new index block and updating at least three blocks. after a while, when there is sufficient free space, things work bhetter. > On Oct 7, 2015, at 9:15 AM, Piotr Ryszkiewicz wrote: > > Update from Progress Community [https://community.progress.com/] > > Piotr Ryszkiewicz [https://community.progress.com/members/piotr.ryszkiewicz] > > Hello Rich, > > Thanks for suggestion, I will increase Toss limit to 400 together with Create limit. > > Regerding most frequently used index - you are right it's not the primary index. But changing dump&load order would help performance only for a while, as new records would anyway be created in primary index order, and queries are most often run on newest, not old data. I am also going to create separate area for each of frequently used indices. > > But still - it does not answer my questions. Why these holes are there after the load ? > > Regards, > > Piotr > > View online [https://community.progress.com/community_groups/openedge_rdbms/f/18/p/20592/72904#72904] > > You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here [https://community.progress.com/community_groups/openedge_rdbms/f/18/t/20592/mute]. > > Flag [https://community.progress.com/community_groups/openedge_rdbms/f/18/p/20592/72904?AbuseContentId=f76f9ef6-3a4c-40f6-aa62-f614005b0078&AbuseContentTypeId=f586769b-0822-468a-b7f3-a94d480ed9b0&AbuseFlag=true] this post as spam/abuse.
Continue reading...
Continue reading...