Meliton Cardona wrote:
How many cards can a stack have?
I believe the only logical restriction is with IDs, so given that the engine doles out a new ID for every object, even cards, regardless of type, the total number of objects in a stack is 4,294,967,295.
However, for most practical uses you'll find that performance begins to bog down at about 5,000 cards, and finds, sorts, and saves are prohibitively slow at 50,000 cards for most uses.
And then there's memory: unlike systems that page parts of the file from disk (DBs, FMP, HC, etc.), Rev loads an entire stack file into RAM. This makes for good performance and more flexibility with when things are saved, making even traditional document behaviors a snap. But it does mean that it can use more memory if you're loading large stack files.
But there are so many ways to work with data in Rev, to help find the one most suited for your project can you tell us a bit about how many cards you anticipate needing and what you want to store on those cards?
-- Richard Gaskin Managing Editor, revJournal _______________________________________________________ Rev tips, tutorials and more: http://www.revJournal.com _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
