Large data stacks - performance

[simplsol at aol.com]

Jacque, Sarah,
I've found that, even at 100 Meg., Rev. handles large stacks more 
slowly than HC, especially opening, closing, and saving (as you would 
expect).
We do an import in HC that moves data on cards in an archive to a newer 
stack. Moving 80,000 records in HC takes about an hour. The same 
operation in Rev. takes 23 hours! This is one of the very few areas 
where Rev is slower than HC.
Paul Looney

-----Original Message-----
From: sarah.reichelt at gmail.com
To: use-revolution at lists.runrev.com
Sent: Mon, 30 Apr 2007 1:28 PM
Subject: Re: Large data stacks - performance

   On 5/1/07, J. Landman Gay <jacque at hyperactivesw.com> wrote: 
  > Has anyone worked with very large data stacks -- say, 500 megs or 
so? Is 
  > there an appreciable slowdown? I have a client who wants to convert 
his 
  > HyperCard stacks as-is, without a database. I'm concerned about 
virtual 
 > memory swapping and other performance issues. 
 
 I haven't worked with anything that large, but I did convert a 
 HyperCard stack that used one card per record. It had about 5000 
 cards. Searching using "mark card" was super-fast in HC and unusably 
 slow in Rev, so I had to convert it to a text file database. 
 
 Since Rev works by loading stacks completely into memory, I would 
 reckon that a 500 Meg stack would not be feasible. 
 
 Cheers, 
 Sarah 
 _______________________________________________ 
 use-revolution mailing list 
 use-revolution at lists.runrev.com 
  Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences: 
 http://lists.runrev.com/mailman/listinfo/use-revolution 


________________________________________________________________________
AOL now offers free email to everyone.  Find out more about what's free 
from AOL at AOL.com.
=0