Hi All -
I am curious if anyone can shed some light on how slack space works on a key sequenced Enscribe file. I looked in the manuals and see small references, but not a great explanation.
If slack is removed from a file using something like FUP RELOAD, that appears to reduce the file size. (Smaller files are typically a good thing.)
However, does this also mean that the subsequent writes to that file will now need to allocate blocks of space prior to inserting a record? If so, I would assume this would decrease the disk I/O efficiency?
Thanks for any insights!
On Thursday, June 29, 2023 at 3:56:38 p.m. UTC-4, wrote:space. RELOAD removes the slack so subsequent inserts can be more expensive by causing new items to move or reorganize existing bytes to provide space for the inserts.
Hi All -
I am curious if anyone can shed some light on how slack space works on a key sequenced Enscribe file. I looked in the manuals and see small references, but not a great explanation.
If slack is removed from a file using something like FUP RELOAD, that appears to reduce the file size. (Smaller files are typically a good thing.)
However, does this also mean that the subsequent writes to that file will now need to allocate blocks of space prior to inserting a record? If so, I would assume this would decrease the disk I/O efficiency?
Thanks for any insights!Slack is configured when the file is created or altered. It comes in two forms: DSLACK (record space) and ISLACK (index space). By default, FILE_WRITEX_ respects these values and leaves slack in the file for future insert efficiency at the cost of
--Randall
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (0 / 16) |
Uptime: | 02:11:54 |
Calls: | 6,669 |
Calls today: | 1 |
Files: | 12,217 |
Messages: | 5,338,567 |