Greetings
First thing I would do is verify which part exactly takes the longest. The 33 Graphs or the task? It's probably the task.
If its the task, one thing you can do is create the task when your
application is loading and verify that task using task.Control(
DAQmxTaskVerify).
This way, you will get the delay hit during application load time
(maybe add a loading dialog box or something). This can be problematic
ofcourse if you do not have enough information about the type of task
at that point. In which case, you can try creating a fake task and
disposing of it to load some of the basic runtime libraries. So this
way, when you load the task the second time, the delay won't be that
bad. We load alot of the dll's at task load time since we don't know
what kind of task will be used and it makes no sense to load all the
stuff in the memory for all cases.
If its the graph (I'm doubtful whether this is the case), try creating the dialog with the graphs and hide it at load time.
I hope this helps.
Bilal Durrani
NI