|
PureBytes Links
Trading Reference Links
|
And those 512 byte chunks are likely to be highly fragmented which will use lots
of extra clusters.
And if you invest in a big disk, you'd better plan on lots of 500 meg partitions
(C through ?) because the cluster size grows quite on big partitions (16k and up
for partitions over 510meg) or invest in an operating system upgrade which
supports NTFS or FAT32 so cluster size is more reasonable - say 2-4k. Of course
that upgraded OS will probably want lots more disk space and need more memory to
handle a larger disk cache ... perhaps even an upgraded processor which to keep
track of all the new bytes.
Earl
Note: cluster size is the amount of space which is allocated to store a file or
file segment which is less than or equal to the cluster size e.g. assuming 16k
cluster size: a 1k ini file will require 1 full cluster or 16k of disk space, a
24k file will require 2 clusters or 32k of disk space, and highly fragmented
files will use minimum of 1 cluster per fragment regardless of content.
-----Original Message-----
From: Jim Osborn <jimo@xxxxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Thursday, July 16, 1998 2:39 PM
Subject: Avoiding Morning Update as Y2K fix
>Since the .dat file is built out of 512-byte blocks, each capable
>of holding up to 120 ticks, those sparse, far-out contracts will
>likely bloat the .dat file far out of proportion to their activity.
>Any day with just a single tick will add 512 bytes to the file.
>
>Since MS Windows fails rather ungracefully as your free disc space
>shrinks, if you can't crunch down that .dat file, you better invest
>in a big disk...
>
>Good luck,
>
>Jim
>
|