UI performance and large data set in Table Object

[mfstuart]

Hi Sarah,
That sounds promising, especially reading prior threads on the same custom
property concept.
(A thought on this concept of copying data to a custom property - wouldn't
it consume large amounts of the users computer memory/resources?)

But this is a multi-user application, where many users will be searching,
updating, deleting, and adding records into the SQL database thru this Rev
app. It's not a read-only application. I think if it was, the custom
property could be worth looking at.
Mark Stuart



Sarah Reichelt-2 wrote:
> 
> On Fri, Feb 22, 2008 at 9:21 AM, mfstuart <mfstuart at cox.net> wrote:
>>
>>  I haven't tried storing data in a custom property as yet, but wouldn't
>> that
>>  render the same lack of performance behavior, where putting the data
>> into a
>>  stack of the UI?
> 
> No, because the engine doesn't have to think about how to display your
> data, it's just storing whatever you put in there.
> 
> I got involved in a project were data was being stored in fields on
> another card, so not even visible. The amount of data was getting
> quite large, about 40,000 lines in each field. When I changed it to
> storing the data in custom properties, the speed of adding new data
> points dropped from around 3 seconds to about 5 ticks!
> 
> 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
> 
> 

-- 
View this message in context: http://www.nabble.com/UI-performance-and-large-data-set-in-Table-Object-tp15618647p15625210.html
Sent from the Revolution - User mailing list archive at Nabble.com.