Making Revolution faster with really big arrays

[Robert Brenstein]

I would not disregard this option so readily. You can use the 
database as an array of sorts allowing you to pull out any set of 
data you need to process and store the results there for later. If 
you are concerned with performance of server-based databases like 
PostgreSql, OpenBase, or MySql, you can try Valentina which embeds 
directly into Rev and is renowed for its super fast performance. To 
reduce disk access issues, get a good SCSI card and a fast SCSI 
drive, giving you additional benefit of having data on a separate 
physical device than your OS and your program.

This solution would be more scalable and portable. It is quite likely 
your data will grow faster than memory capabilities and address space 
restrictions.

Robert Brenstein


>Thanks Pierre,
>
>I considered that also.  A Database application would certainly 
>handle the amount of data, but they are really meant for finding and 
>sorting various fields, not for doing the kind of processing I am 
>doing.  The disk accessing would slow down the process.
>
>Dennis
>
>On Apr 12, 2005, at 5:27 PM, Pierre Sahores wrote:
>
>>Welcome to the Revolution Dennis,
>>
>>Why could you not take help from the native Rev ablity to manage 
>>the process in storing the datas inside an ACID-DB alike PostgreSQL 
>>or OpenBase ? It's how i would handle such amounts of datas, for my 
>>own. Transcript for the RAM fine high-speed calculations and SQL 
>>for the right datas presets extractions could probably open an 
>>interesing datas management way for your process, in about 
>>calculations speed and safety.
>>