Once you start splitting groups, there's overhead on every write where that
occurs, possibly creating a bottleneck. Dynamic files are good for files with
non-consistent item sizes, and also for files with oversized items, but that's
not the case here. I'd go with a "wide & shallow" static file for this purpose,
even if you had to make it distributed to account for size. Since most of what
you'll do with this file is write to it, I wouldn't worry too much about empty
groups.
> Date: Tue, 9 Jul 2013 09:15:20 -0700
> From: [email protected]
> To: [email protected]
> Subject: [U2] File type 30 (dynamic)
>
> I have very little experience with using dynamic (type 30) files and I'm
> looking for some pointers in that regard. I have a file that I am
> considering creating as a dynamic file. The file will be a log file with
> sequential numeric keys. The record size will normally range from about 200
> to 700 bytes, with a probable maximum size of less than 1,000 bytes. We
> expect the file to continually grow without deletions and we will likely
> purge it annually. What are the pro's and con's of creating this file as
> type 30 verses other file types?
>
> Thanks,
>
> Scott Zachary
> UniVerse Developer
> Gardens Alive! Inc
>
>
>
> --
> View this message in context:
> http://u2-universe-unidata.1073795.n5.nabble.com/File-type-30-dynamic-tp41129.html
> Sent from the U2 - Users mailing list archive at Nabble.com.
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
