forum.vdsworld.com

Cipper

Why If I load in table is very very slow (3000 record)

list loadfile,table1,@path(%0)ARCHIVIO.TXT

If I load in list is quickly ?

list loadfile,list1,@path(%0)ARCHIVIO.TXT

Can i resolve ?

jules · Posted: Wed Mar 23, 2005 8:51 am Post subject:

No. It's fast to load a text file into a list because it has no structure, the loader just has to search for the line breaks. When loading into a table, each line has to be parsed into columns and a separate cell (kind of like in a spreadsheet) has to be created for each piece of data. So a lot more work is going on, and that's why it's slower.

Cipper · Posted: Wed Mar 23, 2005 8:54 am Post subject:

Ok, I have supposed, But there is a trick?

Dr. Dread · Posted: Wed Mar 23, 2005 11:27 am Post subject:

jules · Posted: Wed Mar 23, 2005 12:55 pm Post subject:

But he's talking about the speed relative to a table. A 3000 line file should load quick enough.

Cipper · Posted: Wed Mar 23, 2005 2:29 pm Post subject:

650 lines come loaded in 12 seconds, are however a lot for who waits for.

Boo · Posted: Wed Mar 23, 2005 2:45 pm Post subject:

jules · Posted: Wed Mar 23, 2005 2:49 pm Post subject:

Boo · Posted: Wed Mar 23, 2005 2:53 pm Post subject:

But will it work quickly with very large files? Seems to me there was an issue with files several MB in size (even when increasing the buffer)?

jules · Posted: Wed Mar 23, 2005 2:57 pm Post subject:

jules · Posted: Wed Mar 23, 2005 3:08 pm Post subject:

Boo · Posted: Wed Mar 23, 2005 3:15 pm Post subject:

Hi Jules,

I've successfully used a string that's approximately 1.2 MB in size without problems. However, I used the vdsug.dll to write the string to a file. (And it writes FAST.) Wink

Thanks,

- Boo

jules · Posted: Wed Mar 23, 2005 3:37 pm Post subject:

Well in that case I would have thought BINFILE WRITE would be just as quick. I would have thought the memory management of handling the large string was more responsible for the speed than the actual writing to disk. If anything, I would have expected it to be slower passing the data to an external DLL than to an internal command.

Garrett · Posted: Wed Mar 23, 2005 3:45 pm Post subject:

You can do one of two things. First would be to simply hide the table
element while loading it. Second would be to use the @sendmsg()
to stop drawing the element until it's done loading and then send the
message to allow drawing after it's loaded. Either of these will increase
the speed.

jules · Posted: Wed Mar 23, 2005 4:26 pm Post subject:

Nice tip, Garrett. It works with TABLE elements too. Unfortunately when I tried it, it didn't actually make the process any quicker (populating a table) and not seeing anything happening I found more disconcerting than looking at an egg timer for a few seconds.

I didn't try loading a TABLE from a file. Usually with a TABLE element you want to specify a bitmap for each line, and that means adding the data line by line. Even so, I can add about 1,000 items to a table, including determining the icon for each one, and then sort the table, in about 6 seconds, which I don't think is unacceptable.