LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time required for getting DataSet info

I'm interested in hearing about what sort of times others have encountered in getting output from the "List Data Set Runs" and "Read Data Set Run by Id" vis.

It's my first use of datasets and the information is fine, but with 500 datasets it is taking ~30 sec for the above VIs to do their thing (LVDSC 6.1, P4). The time required seems to be a very nice linear function of the nb. of datasets so when there's the 2500-5000 datasets I expect to have in my database, it'll be ~3 to 6 minutes. This will really mess up my intended use of them in a quick user interface.

If it makes any difference, the number of tags in my dataset is 0 (zero). I'm just interested in the start time, end time, and description.

TIA.
=====================================================
Fading out. " ... J. Arthur Rank on gong."
0 Kudos
Message 1 of 3
(2,713 Views)


Hi Donald,

I can't give you comparable numbers as I am on DSC 7.0. But here's something that might be of interest to you:

1. If all that you are interested in is the Start time, End time, (of the runs, and not traces), and the Description, then you can make-do with just the 'List Data Set Runs' VI. This VI returns this info' for all the Runs in a given DataSet. You would unbundle the 'data runs' cluster to get this info'. You do not need to use the 'Read Data Set Run by ID' VI.

The 'Read Data Set Run by ID' VI internally basically looks-up the run, if found, gets the trace info' for each tag in that run. These are expensive operations by their nature.

Also, normally, the Description remains the same for Runs within a DataSet. If thi
s is the case with you, you just read the Description from the first Run. (Of course, it's very much possible that the Description changes from run to run. In that case you got to read all).

2. In DSC 7.0, my 'List Data Set Runs' VI takes about 4 seconds to return 500 runs. And about 7 seconds for 1000 runs. I have one tag in my DataSet but no description. This is way faster than what you are seeing (plus my test machine is a crappy 450MHz P3). I know DataSets and Citadel in general has improved considerably in DSC 7.0. DataSets are now built into Citadel. You may want to get an Eval copy of 7.0 and see if the difference is as significant as we're seeing here.

Hope this helps. Please write back if you want to discuss more.

Regards,

Khalid


Message 2 of 3
(2,713 Views)
Thanks for your input, Khalid.

Re 1): I had actually gotten rid of my few uses of “Read Data Set Run by ID” when I saw the increase in time last week (I have about 80 sets/day) and went with unbundling the info from “List Data Set Runs”as you suggest. My use of the Description had yet to be implemented and unless someone using DSC 6.1 pops in with reasonable times, I think I’ll trash my use of datasets for now.

I regret that upgrading to DSC 7 isn’t going to happen ... maybe 8 (I don’t want to do a jump like 2.2 to 6 again).

Thanks again. Donald
=====================================================
Fading out. " ... J. Arthur Rank on gong."
0 Kudos
Message 3 of 3
(2,713 Views)