<br><font size=2 face="sans-serif">Shari,</font>
<br>
<br><font size=2 face="sans-serif">The biggest stack I ever made was around 70MBs with 7 levels of data all interelated.</font>
<br>
<br><font size=2 face="sans-serif">The key to speed (and this was HC!) was to link the data to the right cd id and then grab</font>
<br><font size=2 face="sans-serif">the data from there. Access times were less than 3 seconds - it took 3 days to build or</font>
<br><font size=2 face="sans-serif">update the links though! </font>
<br>
<br><font size=2 face="sans-serif">Size was not important as it was for a CD but despite cd speeds (way back then it was 4X), </font>
<br><font size=2 face="sans-serif">was really snappy!</font>
<br>
<br><font size=2 face="sans-serif">The scheme was a display stack with browsing controls and 7 hidden stacks. The 1st level</font>
<br><font size=2 face="sans-serif">stack contained the index to the cd IDs holding the data and their respective parent and child</font>
<br><font size=2 face="sans-serif">links (also stored as IDs). IOW, a classic double-linked list. </font>
<br>
<br><font size=2 face="sans-serif">It didn't require much ram and it was the fastest I could find in the year's time it took to develop.</font>
<br><font size=2 face="sans-serif">I had planned using an XCMD in the beginning but none could handle the amount of data! </font>
<br><font size=2 face="sans-serif">Even FileMaker had troubles! There were some 800,000 record links for 80000 items!</font>
<br>
<br><font size=2 face="sans-serif">Hope that helps a bit! ;))</font>
<br><font size=2 face="sans-serif">Xavier</font>
<br><font size=2 face="sans-serif"><br>
---------------------=---------------------<br>
Xavier Bury<br>
TNS NT LAN Server<br>
ext 6465</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Brian Yennie <briany@qldlearning.com></b></font>
<br><font size=1 face="sans-serif">Sent by: metacard-admin@lists.runrev.com</font>
<p><font size=1 face="sans-serif">28/08/03 02:20</font>
<br><font size=1 face="sans-serif">Please respond to metacard</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: metacard@lists.runrev.com</font>
<br><font size=1 face="sans-serif"> cc: </font><font size=1 face="Arial">^</font>
<br><font size=1 face="sans-serif"> Subject: Re: Squishing data</font>
<td></table>
<br>
<br>
<br><font size=2 face="Courier New">I'm not sure what you mean by "putting data in an array" changing the <br>
stack size: arrays are held in memory. Do you mean that you write the <br>
arrays to custom properties?<br>
<br>
You may want to try using compress() on the field data, i.e.<br>
set the compressed_data of fld 1 to compress(fld 1)<br>
<br>
Then just access the fields with:<br>
put decompress(the compressed_data of fld 1) into fieldData<br>
<br>
For performance, you would want to only decompress() once- although <br>
keeping the uncompressed data in memory bumps your memory requirements <br>
so you'll have to balance memory vs. performance.<br>
<br>
Compress() should get you a reasonable shrink on text, hopefully 50% or <br>
so.<br>
<br>
Brian<br>
<br>
> The stack with 300 fields is about 15 MB. I tried putting the data <br>
> into an array, and deleting the fields. But it actually makes the <br>
> stack bigger to do this. I created an array with 300 elements, <br>
> myArray[1] held the data from field 1, and so forth.<br>
<br>
_______________________________________________<br>
metacard mailing list<br>
metacard@lists.runrev.com<br>
http://lists.runrev.com/mailman/listinfo/metacard<br>
</font>
<br>
<br><CODE><FONT SIZE=3><BR>
<BR>
Visit us at http://www.clearstream.com<BR>
<BR>
IMPORTANT MESSAGE<BR>
<BR>
Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.<BR>
<BR>
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.<BR>
<BR>
END OF DISCLAIMER<BR>
</FONT></CODE>