On Feb 20, 10:11 am, christophe albrech <[email protected]> wrote: > But it can have performance implications at the DB level. > > - If not sequential, Index fragmentation ensues. Page splits, too. > - As the UUID is probably the clustering key, it gets added to all NCIs, > which in turn become larger and slower. > - Database gets bigger. That means less stuff in proc and data cache, > more io, longer backups and disaster recovery procedure. > > That said, they are, indeed pretty useful to move stuff around. And using > sequential UUID does a good job of limiting the damage. No idea what far > cry does under the hood though, so I'll stop bitching. > > Tof
FarCry doesn't lock you into anything in this regard, you can avoid fragmentation and page splits by making objectid a non-clustered index and setting your clustered index to something more suitable, as you would do in any database that you needed to tune for performance. For those content types with millions of rows you'd also set bRefObjects to false in your component to avoid writing to FarCry's "master" table of objects and specify the content type name in any ORM related functions, instead of letting FarCry look it up automatically. cheers, Justin -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
