Jack, I didn't mean you should actively try to change the way the OS allocates harddkisk space for GN. The assumption is that you have a harddisk that isn't much fragmented to begin with. Given that, GN tells the OS to allocate a big chunk of harddisk space, in which case the OS will automatically try to use the largest chunks still available.
For example, Total Commander uses pre-allocation before it copies large files from one partition/disk to the other. Winrar pre-allocates space prior decompressing a file. Bittorrent and eDonkey clients, download managers like Flashget, will allocate enough space on your hard disk for the file you want to download, which can sometimes take a couple of seconds depending how large the file is going to be.
One way to deal with fragmentation is to periodically run a defragmentation utility like the Speed Disk component of Norton Utilities. Another way is to put the database all by itself in an empty partition so it can allocate contiguous space as it grows. A third alternative is to use the ALTER DBSPACE statement to preallocate more than enough space for future expansion.http://www.sqlservercentral.com/columni ... ersion.asp
If the ALTER DBSPACE approach is used on a disk that is initially unfragmented then you will avoid future problems. That's because your database file will continue to use contiguous space even if the rest of the disk becomes fragmented.
The ALTER DBSPACE approach also avoids another performance bottleneck where SQL Anywhere must take time to allocate and initialize more disk space every time it runs out.
Avoiding fragmentation of database fileshttp://www.ianywhere.com/developer/prod ... 000332.htm
To keep fragmentation in the database files at a minimum without defragging them you should avoid using the autogrow setting in SQL Server for them. Preallocate enough size for them from the start and when growth still is needed try to increase the size in large chunks at once. Also make sure you keep the database files on separate disks away from other files to make sure logical contigous space is available for them. Separating the data files from the log file is helpful and also important for performance in other ways, since the log file is written to sequentially.
Rapidly-changing database files can lead to excessive file fragmentation on the disk, resulting in potential performance problems. Unless you are working with a database with a high rate of change, you do not need to worry about explicitly allocating space for database files. If you are working with a database with a high rate of change, you may pre-allocate disk space for dbspaces or for transaction logs using either Sybase Central or the ALTER DBSPACE statement.
Thank you for making this a priority. I haven't tried the "Compress data after cleanup" feature yet simply because I didn't want to clean-up yet
I don't like to globally delete news items older than x days - waiting for GN to have individual feed preferences for max item age.