Project Manager - Loading Time

I think I mentioned the following issue before on the forum, but it's driving me nuts and I just want to know if can get some updates.
"Here is the deal"
1) You set up your scan path for the Project Manager and let it index all the relevant files
2) Project Manager writes the index data to the "~/Library/Preferences/Logic/PM Data/LogicProject7" file. The more files you index, the bigger the "LogicProject7" file.
3) Logic also writes an invisible file called "Logic 7 Database" to the root level of all network volumes it is indexing
3) When you start Project Manager, it seems to read those files and updates them when you work in Logic.
"Here is my problem"
I have a fairly big amount of data siting on an XserveRAID (Logic Songs, Loops, EXS, Audio files, ...). I don't know the exact size, because I exclude some of the nested directories and try to index only the relevant files. I guess the total is getting close to 1TB.
The Project Managers index file "LogicProject7" is now 127 MB and the launch time just for the Project Manager is 7 minutes . That makes it impossible to use the "start Project Manager at startup" feature. As we all know, Logic still crashes once in a while and adding the 7 minutes to the already long launch time (reading the EXS instruments), I would end up with close to 15 minutes launch time.
I don't understand where the bottleneck is. The progression bars of the Project Manager during startup (building tress, etc) are crawling like a snail despite a G5 dual 2.5GHz and a Gigabit connection to the Server that is connected with a dual Fibre Channel to the RAID.
The Activity Monitor shows Logic with a 30% CPU utilization and the network shows the activity with 60kB receiving and 30kB sending which is more or less constant during the startup process. Is the reason for that, because Logic is not optimized to use the full bandwidth and CPU power.
"Here is my question"
1) Does anybody have more insight into the Project Manager's functionality in regards to speed.
2) Can you post your reference: "LogicProject7" file size vs Project Manager startup time
Thanks

First of all - iSchwartz - you are not only okay, but also one of the most friendly and in depth advisers here on many subjects.
Now stop biting your nails - please! What are you gonna do with all that excess calcium?
You are indeed blissfully unaware of the benefits of this often overlooked PM thing (TG it's not a PMS thing...). If you are happy with EXS loading times, are never asked for multiple choices regarding the location of a sample, and your system runs stable, then don't change anything.
Es wird Dich nicht eines Tages in den A.... beissen!
Check your EXS loading times. Mine improved dramatically. Admittingly I have to confess, that my PM is overseeing, tracking and updating a little less then Edgar's, about 800 GB.
P.S.: Would you mind posting a picture of you in the newbie beanie?

Similar Messages

Load time

What is the load time in a project?
What is the calc time in a project?

load time depends on many factors like how much data you are loading and your order of dimension in load file. you can know more about load time in optimizing the load data in DBAG.
Same case with Calc time, as said before you can know about it in 'Using Simulated Calculations to Estimate Calculation Time' in DBAG.
hope this helps

Ultra slow project load time

I was wondering if anyone else has encountered this problem and can point me to the solution.
After capturing 40+ hours of footage in a new project (log and capture only), every time I try to load the project it's a 10-minute affair.
I'm wondering if I'm low on memory (see 3GB and other specs below) or if it's my Firewire 800 LaCie drive. All the clips are either HDV or DV (NTSC), so nothing out of the ordinary.
If I need more memory, I'll get it. Just want to identify the problem and not throw money at random solutions. Any help would be appreciated.

Well...I broke. After waiting 20 minutes for the project to load up (for about the 25th time), only to do 'spinning beachball' every time I try to work with the project, I've decided to start the capture over again Hello, 40 hours of re-do capture time.
This time, all project files and media will be captured/stored on my CalDigit S2VR Duo drive (thanks Shane for the nice review and why I went this direction instead of G-Tech). Hopefully, this problem won't rear it's ugly head again on the new striped RAID drive.
I can only assume that it's one of two things: (1) I had some bad media in the whole mess and it's freezing the system when trying to access the project and relink video clips/files or (2) maybe the LaCie drive is on it's last leg. I don't know, but in the long run, it may take just as long (with the frozen state of the project) to figure it out as it will to recapture.
I will post back with an update once I've reached the 'old' video capture point on the new project file (on the new drive).
And before someone asks, the Media Manager was working just as slowly as the loading of the project, making it impossible to try and re-capture the project onto the new drive through FCP.

Captivate project takes long time to load on LMS

So I developed a bunch of Captivate 7 modules for a course I'd been working on for some time. When I finally loaded these up on the LMS, I notice that when the modules are launched, a pop-up window opens with a grey background and just stays like that for up to 3-4 mins. I figured grey, because that's what I had set as the HTML page color in the skin editor. However the actual module contents take really long (3-4 mins) to load up. When I tried running all these modules locally from my computer, the grey screen fades into the splash animation within a second.
I figured that this was either due to a bandwidth issue or the LMS causing problems. So I then had these modules tested from our India and US offices (different internet connecttions, multiple LMSs). Same thing happened, takes up to 3-4 mins to transition from the grey screen to the splash animation (but loads up instantly when run locally). We then tried this on multiple LMSs like SABA, Moodle, and even tried this on SCORM Cloud and the same issue. The modules takes a long time to load up, so I kind of ruled out the LMS/bandwidth being an issue.
I'm speculating here, but what I think is happening is that the SCO is trying to download the entire module (about 10MB) to the users machine before it plays the splash animation -- if that's the case then is there a way to avoid that? I mean I don't want a 200 slide Captivate published project to be downloaded right from clicking the launch button -- it could stream through as the user advances through the module. Also, I've seen some pre-loader and Start/End options but not sure how those work.
Important to note here, the 3-4 min wait time from when the module is launched, is only for the first launch. If I were to close the browser popup (in which the SCO opened), and click launch again from the LMS, it's loads up almost instantly -- so I'm pretty sure something's happening in my Captivate project's loading settings which I can't put my finger on.
Can anyone help me figure out why this is happening and also what are some possible fixes to this. I can assure you that it's not an internet bandwidth issue because we've tested it on multiple internet connections and on several LMSs (even the client's LMS that this was tested on says that the initial load up takes too long).

All the symptoms you quote sure sounds like a bandwidth issue to me.
Obviously when you load a project directly from your hard drive then there's no issue with bandwidth. But if you're pulling down 10 megs from a web server and it takes a while to start then bandwidth is the obvious issue. I agree that 3-4 minutes sounds excessive for a 10 meg file but that depends entirely on how many users are sharing your bandwidth. Try getting your people in these different locations to visit one of those websites that allows you to test your actual bandwidth. It might not be as much as you think.
On another note...What do you have your preloader set to? The default is 100% but you can usually set it to something like 25% without too much trouble. That should cut the start time down appreciably but nothing is going to eliminate it completely because there'll always be some initial lag the first time your learners view the content.

Use of MS Project Management 2010 to Manage Multiple projects over a given time period

Is there some information (article/s) I can research about using MS Project Management 2010 for managing multiple projects over a given time period? I'm being asked by a potential client to take a job as a Program Manager to manage five projects all
at once. Each of the projects has it's own MS Project Management software, project leader, and project team. An overall project plan has to be put together to manage this large project. There are some dependencies with these projects inorder to complete
on a specific date.
Thanks

SSCDML --
In order to manage this program of five projects using Microsoft Project 2010, I would recommend you do the following:
Create a shared resource pool file containing the resources in all five projects.
Connect each of the five projects as sharing files with the shared resource pool file to share the resources.
Create a master project for the program containing each of the five projects as subprojects.
In the master project, set cross-project links as needed to show dependencies between projects.
Hope this helps.
Dale A. Howard [MVP]

How to manage wait time in between pages loading

Hi,
Could you please help me "How to manage wait time in between pages loading while playback script using etester?
Thanks,
RJ.

RJ
You can edit the think time in eTester by:
Expand the tree node and right click on the address bar to select Address Properties, you can then edit the text box called Delay Before PlayBack
If you like to specify think time between actions instead of action groups: right click on the actions ans select properties, there are 2 text boxes in the new window; one for milliseconds and the other for seconds
Hope this helps
Alex

How to reduce project load time?

I am currently working on a large project (25+ Mb, thousands of vis) with something on the order of 100 classes. Opening the project is painfully slow. It usually takes 7-8 minutes. I'd like to figure out a way to reduce the load time.
What is LV's behavior regarding loading project file vis and libraries (lvlib, lvclass, etc.)?
Are all items in the project automatically loaded when the project is opened?
Are items not in the project but used as sub-vis automatically loaded?
Are dynamically linked items not included in the project automatically opened? (I imagine not.)
Are dynamically linked items that are included in the project automatically opened?
Thanks,
Dave

Hello,
I have talked to multiple people about your issue and we honestly believe that you you are experiencing is expected behavior based on the size of the project and number of VIs used. Creating a new project will sometimes help when a project file has a corruption within it. Since you are experiencing the same behavior on multiple computers, any difference in load time will be a function of the speed, RAM, etc. of that particular computer as compared to your machine. In saying that the files are technically loaded, I am saying that their locations are known so that when they are called, they can be loaded into memory as needed. It does not have to load any portion of the VI other than the location on disk. I would not expect either of those methods to reduce your project load time. Switching to dynamic linking only changes the order in which LabVIEW searches for the files. As I stated before, files added to the project are defined by the name and location on the disk. You can think of the project file as an XML file with different pieces of information about the files. If the file cannot be found, it will try to dynamically link the files by searching for them on the disk. When this happens, it goes through a seris of locations where the files might be located. When the project is loaded, it looks for the files that are listed in the project file first. I hope this helps.
-Zach
Certified LabVIEW Developer

Managing your time on FCP projects, knowing when to say when.

I have a question for you people out there. How do you know 1) how long things should be taking you, and 2) When you are caught up and when you're not, 3) when to say when?
In the various professions I"ve been in, I"ve either gone in to work, then left for the day, or done a job that takes a few hours and been, well, done for the day.
I'm finding that working on larger projects that might take weeks or a month, I can't relax and do anything else, because it feels like I'm never finished as long as something remains to be done. This is probably aggravated by not really having a sense of time as to how long something should be taking, due to inexperience. So it feels like each project eats up my life with no end in sight.
But if you are working on larger projects, and eventually it will be several at a time, I'm never going to be 'finished,' as long as I am in business. And when your office is in your bedroom, it's always there looming - although I did recently move it into an armoire to visually make it go away. Still it's hard to take a day off, or go out with friends, or concentrate on other life areas when you know you still have so much stuff waiting to be done. And even when it is done, there are still tutorials, skill development tasks, I can work more on the demo, etc.
Your take on this? Has anyone who has been doing this longer, solved this? I love my budding business but want to have my life back also, and want to be careful not to burn out before things even get going.

Thanks for the many awesome suggestions you guys. These boards are such a great place to learn how other people do things!
Do you guys plan out your whole project - log your time codes, log your shots for capture, do some kind of storyboard, or other types of planning? Or do you just dump the whole tape to capture? I'm curious what people's workflow is that helps them stay organized and cut time.
Try to anticipate every possible disaster and have a workaround in place.<<</div>
Yes I am learning this, for sure! Sometimes it's just inexperience - that whole area of stuff you don't know yet. But sometimes it's just haunted equipment. I did a DVD for an anniversary couple, and had been up all night. Reluctantly I told them I would go do the presentation since their setup woudn't work for whatever reason, I don't remember now. I went home to add something in and burn a new DVD. The entire project crashed in DVDSP - would not open - missing file reference blah blah blah ... and I had to rebuild the entire thing from scratch right then. And then, a cord broke at the presentation - but because of forethought, I had another on hand.
Then there was the "Compressor" fiasco (See the "I can't believe this! F#%$&* Compressor!" thread) at 3 AM. Etc. But even though it was the eleventh hour, because I had planned ahead and left extra time, it allowed for time to correct problems with the drives and sequences that arose earlier that week. It all got done. Otherwise it would have been hosed.
in the second week i did 2 all-nighters in a row, and at the end of the last day I was in tears and on the phone to my mum... professional huh?<<<<</div>
Oh man I feel yer pain. LoL - first job - except in my case it was the best friend. And I was up all night, also. Thanks so much to the people on the board who carried me through that and patiently answered the most basic questions. It's embarrassing to remember them now. I did not anticipate how steep the learning curve would be and threw myself into a job without even understanding basic concepts. With the best of intentions - I didn't realize what was involved and I thought it would be a simple project that would be easy to learn-as-you-go. I thought "hey, I'm a quick study - got a graphics background - great on a computer - piece of cake!"
Fortunately the learning curve has kicked since then but it sure was trial by fire!

Very slow load times on EXS24 instruments?

Hi everyone - I have a troublesome problem..
At the moment this only seems to happen garage band instruments loaded in exs24
When I try to load instruments from garageband i get to enjoy the spinning wheel and about 3 minutes of load time [and this wouldnt be the first stime i would have loaded the instrument]
When it does finally cease spinning it asks me to choose between the garage band samples, or dupe sampler files in self contained projects.
I always pick the garageband directory..
Is there a way to decrease the loading time?

This tends to happen when you have more than one copy of the EXS sample on your drive network. As soon as EXS sees two of a sample, especially if there is no existing direct link in the EXS instrument, it will tend to scan your whole system for any and all potential duplicates. This can take a while.
My only suggestion is delete the duplicate samples and make sure your instruments all contain path links to the appropriate samples. Bear in mind that if you store samples in the project folder, at least those should be found quickly, but it will not solve the problem of loading new patches into the project.
To be able to find and get rid of duplicate samples and re-establish the links in a batch fashion, I highly reccommend EXS manager by Redmatica.
www.redmatica.com

Project Manager: How to include the Trash as an Exclude Path

I'm delving deep into the wonders of the Project Manager. Wondering if there's any way to add the Trash (on any drive) as an "exclude path" so that I can prevent the PM from going 'dumpster diving' for files in there.
While on the subject of trash (OT) I really miss the OS9 trash scheme where you had an actual desktop icon for the trash. Also, when you'd open the trash in OS9 to see what was in there, a tally of the total MB/GB of trashed files would be displayed in the finder window. But not in OSX (why?!?!). Anyway, does anyone know how to achieve either a desktop icon and/or a file-size count of trashed items in OSX?
Thanks, and Happy New Year!
-=iS=-

Surrrrrrre Dahlin'.
Somebody in this forum said, it's the time of Red Red Wine.
I am following this advice. Wait, is that party over already?
Truly, the PM being as powerful of a tool it is, sometimes needs our (human) input to get it back in shape. Even the PM preferences DO GET STALE over time.
One SI after another started to load really slow over here. Sometimes I even had multiple choices from where to take the samples from. Now I know, that I have some duplicates with all my drives attached, but PM designs a structure regarding where to look first. So, I re-scanned those folders concerned. Sure enough, no more "duplicates" messages and loading time was great again. Except for files I did not access since a long time, or files I never loaded.
Yes, I trashed my PM preferences (user/library/preferences/Logic PMData).
Did go to Window > Project Manager > Functions > Expanded Scan, with all my drives attached.
Then I went to bed.
The next morning, I saved the PM data, quit LP, restarted my computer and... voilá: EXS loading times are up to speed again.
All under the influence of Red Red Wine.
It works well.
Summary:
Set up as explained above, go to sleep and be amazed about the power of the PM.
No punishment involved.
Tschüß.

Project Management Question - timelines for Production system deployment

Hi
I need an expert advice on setting up timelines for establishing an Oracle Apps Production environment. We are implementing Oracle HR & Payroll at an organization.
Our system architecture is a 2-node application tier and 2-node DB tier (RAC). RAC is configured by another party and we only have to prepare the application tier (2 nodes)
We would be installing Oracle Apps R11i (11.5.10) with jserv load balancing on the 2-nodes
Can anyone suggest how much time this should take to install/configure & patching of the application tier (on 2 nodes)?
Regards
Saira

Duplicate post (check your other thread):
Project Management Question - timelines for Production system deployment
Re: Project Management Question - timelines for Production system deployment

Premiere Pro Project Manager does NOT include After Effects files.

Warning: Premiere Pro "Project Manager" does NOT include the After Effects 'dynamic linked composition' files associated with the project when "Collect File and Copy to New Location" resulting in the incomplete and loss of all dynamic linked compositions in the new project destination ( folder or disc drive ) .. I know this also includes Photoshop dynamic links and assume includes Audition audio files as well.

Here's the best way: Personal Responsibility.
Put all of your project files in one file. Stop asking PPro to do it for you. It's simple. This is a no-brainer. If you create a linked comp, create it in the same file as your PPro project and files. When you send it to Encore, create the Encore project in the same folder. Works all the time, every time. When you're sure that you're finished with the project for the forseeable future, move the entire folder off your workstation into storage. Do I move a copy of each asset (video clip, image, audio, etc.) into this folder before I import it to my AE or PPro project? Yes I do. Is it overly time-consuming? Not really. I can fly on my machine. Does it beat not being able to open a project later. Oh yes. Yes it does. I'd say I did 50 projects last year this way. When I occasionally had to move a project folder back to the workstation, I had no problems. Everything worked as it did before I off-loaded it. That's because I take personal responsibility for my projects. It's imporatnat that theyt work, especially if I end up having to hand it off to a third party down the road.
BTW, my workstation is RAID 0. If you are using anything less, you need to upgrade. What I'm trying to tell you is that my system works very well. I have not always done things the right way. I have had my share of frustration. The point is that I learned. Now I'm passing that on to you. I use CS5 on an HP Z800 with a measely 12 gigs of ram and a single i7 quad core and the aforementioned RAID 0 configuration and a hacked Nvidia GTS 450. It works quite well. I'm sure I would do even better with another i7, 12 more gigs of ram and a Quadro 4000, but this is what they give me to use.
Additionally, I'm using CS5 at home on a MUCH older HP xw8200 dual dual Xeons, 12 gigs of ram and software-only MPE. Guess what? It works quite well.

Auval crashes / long load time exs24

hey, after having being able to solve a nagging problem fast in this forum, I'd like to post about two other things that bother me
1) Choosing EXS24 patches takes extremely long time
Every time I try to load a EXS24 preset, it takes a very long time until I actually can use the preset. This is absolutely unacceptable as I can't just try out a preset. Very annoying. I read somewhere that's because EXS seems to encounter some duplicates. However, I do not have duplicates - anymore. I have an external backup drive; exs may have found duplicates on a backup there. But all this annoying waiting happens also when the external drive is not attached. I read there is a cleanup software - but this is clearly a bug and I do not want to buy a software just to have normal response time! I am not using exs at all because of this and that's not ok. Any suggestions?
2) Every time I start Logic Pro 7, I get an error message stating that "auval" (I think that's the name) crashed. Seems to be the plugin validator or something. I can continue using Logic without problem, but I'd like to know if there is any solution to that, don't like to click away an error message every time.
Every suggestion appreciated
thanks

Logic Pro 7.2 is still installed in the exact same path in the Application folder as at the first day. I never moved the installation folder.
Where Logic is is not relevant, it's where the samples are in relation to where the instruments think they should be that's the issue.
So where does Logic Pro look for the samples? Why can't it find them?
Each EXS instrument file contains a list of samples, like:
/Volumes/MyAudioDrive/Samples/SwingingCats/SmallRoom/miaooowwww.aif
/Volumes/MyAudioDrive/Samples/SwingingCats/SmallRoom/miaooowwww2.aif
/Volumes/MyAudioDrive/Samples/SwingingCats/SmallRoom/crash.aif
So each sample will be loaded from those locations stored within the instrument file. If Logic tries to get /Volumes/MyAudioDrive/Samples/SwingingCats/SmallRoom/miaooowwww.aif and fails (let's say the drive isn't mounted, or that directory doesn't exist, or that directory does exist but the correct samples aren't there, then Logic will attempt to search your file system for where the right sample actually is.
What in fact is different from the original installation is my username with which I use Logic - so does LP look in my home folder? Can I fix this in one go?
So, if your sample content that is causing the problem is in your user folder, then for instance, an instrument file might be looking for:
/Users/MyNameIsSteve/Samples/wazzoo.aif
and if your home folder is now called "ItsChangedToBarbara", clearly, the directory referenced to in the instrument file is no longer there, causing Logic to need to search for where your samples now are (/Users/ItsChangedToBarbara/Samples/wazzoo.aif)
Can I fix this in one go?
Yes, as mentioned, Logic's project manager can do this.
It is in fact how you say, I loaded an empty project file, loaded exs, loaded a preset - took a long time. didn't save it, closed, re-opened it, and this time exs loaded the preset immediately.
And from my explanation of the behaviour, you should understand why now.
How to relink ALL files in the project manager?
Do a full scan, select the EXS instruments you want to relink, and use the "relink samples for instruments" operation, I forget the exact wording.
Unfortunately, there is no nice error message, auval just crashes.
Have you looked at the crashlog?
So I have no idea which of the many plugins I have causes the error. I use only
Native Instruments plugins from the Komplete 5. And I would not even know how
to remove that plugin, as when one installs a program, everything installs
automatically (there must be something like a VST folder somewhere?)
Logic does not use VST plugins. The AudioUnit plugins are installed to:
/Library/Audio/Plug-Ins/Components/
/Users/YOU/Library/Audio/Plug-Ins/Components/
Temporarily move the plugin component files out of there, and add them back in until you find the one that is crashing validation.

Project Manager: Why?

I just had opportunity to rebuilt my entire system from a zero'd drive. Upon running Logic for the first time I couldn't help but notice how much faster it launched and how much quicker it was ready to do business than it has in recent weeks. And what was different about the past few weeks that Logic became slower? Well, I started using the Project Manager (PM), doing scans, resolving file references. In short, I started using the PM and I'm not sure to what benefit.
Since my foray into the PM, Logic would load with prolonged PM messages, including "updating tree". We're talking about a few seconds here and there, so no big deal, right? But still, before venturing into PM world, I never saw anything more than a blip of a dialog about "updating tree".
Upon further reflection, I'm having trouble understanding the point of the PM. What I'm going to do is describe my understanding of how I think Logic works, and I'd like to know if I'm missing some big important point of the PM. But here's where I'm at now...
I came to L7 from L4 where there was no PM feature. I lived fine without it. When I saved a song, the paths of the audio files lived in the logic file, just as I imagine they do now. If I was missing a file, Logic's search engine came up asking me where the file was. Simple enough.
When I came to L7 and started using EXS, I RTFM about file organization but blissfully ignored the chapter on the PM. Unless I did something stupid and renamed a file in the Finder, songs loaded fine, sampler instruments loaded fine, what could be simpler? So at this point I'm totally ignorant of the purpose of the PM, yet I still had success running Logic.
So... back to last night and the re-building of my system. Without doing a PM scan, I tested out EXS and was able to load up my sampler instruments just fine. In fact, some sampler instruments that Logic used to choke on (after doing the requisite work in PM to resolve file references) loaded up incredibly fast with no "where is the file..." dialogs. Now, I imagine that this is because the sampler instrument itself contains the path to the required files. Same logic as a song file containing data about which audio files to use. So who needs the PM to keep track of this stuff when file paths are already contained in songs and/or EXS instruments?
The kicker came when I looked at PM today, and saw that it had only "caught" about 5 of 20-odd sampler instrument folders.
So at this point, my feeling towards PM is:
1) it doesn't change Logic's ability to successfully recall audio or EXS instruments
2) running scans ends up increasing Logic's boot-up time
3) running scans may indeed keep you busy for quite some time answering dialogs about which file is needed for various songs and instruments
4) EXS instruments load faster now than they did after hours of scanning/tinkering with the PM
So, someone please enlighten me. What's the point of the PM then? I'm all ears/eyes...
-=iS=-

Hey X-man,
Well... you asked, so I'mma tell ya... [exhales, then... begins]
So clearly there was something majorly wrong with my 'puter cuz the Jeanius had to reset the firmware. G*ddammit if I know what I could have possibly done to cause something like that to become necessary. It's not like I ever tinker with Terminal or any of that Unix crap. OK, OK, I admit it. It's not crap. My inner geek would love to know how to program Unix, but there's only so much time in the day. But I digress...
So yes, it's possible that because the firmware needed to be reset that in the interim my computer was acting funny as a result, causing problems with applications like Logic. But I don't really know that for sure; don't know enough about how it all works to even make an educated guess. For all I know the firmware reset became necessary only after the kernel panics and not before. Again, I don't know enough about this stuff to debug it. And at the end of the day, to paraphrase Bones from Star Trek, "Dammit Kirk, I'm a composer, not a computer expert" (the original line was "I'm a doctor, not a tree surgeon" LOL). This kinda stuff is just waaaay outta my field of expertise.
Anyway, my decision to forego the PM is pretty much outlined above. I don't think it's necessary for 99% of normal, everyday operation of the program. Just like Hyperedit. I never, ever, ever, ever use it. Sure, it's a feature of the program, but I just have no use for it. Can't see the need to either because my editing techniques don't require that tool. So to me, Hyperedit is redundant.
Same with PM. My saving project technique is, I think (hope!!) adequate enough that I don't need the PM to help me link files. All that info is already contained in the song file and/or EXS instruments so I think that to a large extent, PM is redundant (except for the few benefits I described above).
How well does it even work? Well, prior to my 'puter's meltdown I saw first-hand that PM wasn't able to resolve various file references. For example, it couldn't find any of the movie files associated with my various cues over multiple projects (these all appeared in red in PM). But if I loaded up a song, the movie file opened just fine in Logic (cuz the file saves the reference to the movie file). Conclusion: PM can't find the data and that's OK cuz I don't need it to.
Let's say for argument's sake that my computer's pre-meltdown condition led to errant behavior of the PM. The only way I could figure out if PM is working correctly now (on my virgin system) is to run it through its paces. But we're talking about hours of downtime while it does its thing (I think it would be best to leave the computer alone while doing an extended scan for various reason). Is it worth the time-investment? At this point I've simply decided that it's not. Maybe I'll eat my words one day, but for now I'm comfortable with this decision.
And of course the other thing this means is that sonther will never speak to me again... So don't tell him you saw this, OK?

Improving load times in Linux LabVIEW executable

I'm looking for (simple) ways to improve the loading times in a Linux LabVIEW executable. We're using a low performance, low cost CPU board, and loading times are terrible. The CPU is capable of doing everything after the application is loaded, but takes forever to get there.
One of the problems is the size of the executable, that grows everytime you just look at it. Are there ways to create smaller executables? It runs from a Compact Flash card, which is ofcourse much slower than hard disk.
Another problem is a dynamic vi, that is started for every TCP connection that connects to the application. It takes a long time to load, and connecting too fast can even effectively hang up the system. Starting a handler task takes about half a second, up to a few seconds for the first task.
We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.

Dennisvr wrote:
I'm looking for
(simple) ways to improve the loading times in a Linux LabVIEW
executable. We're using a low performance, low cost CPU board, and
loading times are terrible. The CPU is capable of doing everything
after the application is loaded, but takes forever to get there. One
of the problems is the size of the executable, that grows everytime you
just look at it. Are there ways to create smaller executables? It runs
from a Compact Flash card, which is ofcourse much slower than hard disk. Another
problem is a dynamic vi, that is started for every TCP connection that
connects to the application. It takes a long time to load, and
connecting too fast can even effectively hang up the system. Starting a
handler task takes about half a second, up to a few seconds for the
first task. We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.
I'm
not sure about the first part of your question. LabVIEW is highly
binary and does a lot of memory allocations before even one VI is ready
to be started. So maybe the memory manager is a problem. Another issue
is that the Macintosh like resource file format that is used by LabVIEW to store its VIs etc. results in
lots and lots of individual disk accesses with a rther random like
character inside a single file. So if you can configure the read
caching of your disk to use more memory this may significantly increase
the speed of loading LabVIEW VIs or applications.
And finally spawning VIs through VI server is a rather costly operation
especially on low resoruce systems. A VI is more like an executable in
many ways as far as resource consumption is concerned rather than a
thread. A much better way would be to avoid spawning subVIs altogether
and implement a queued TCP/IP server similar to the Date Time Server
example. It is a little extra work to work with this shift register
architecture but it will not have the issues of long load times for
every new TCP/IP connection coming in.
Rolf Kalbermatter
Message Edited by rolfk on 03-07-2006 06:33 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Project Manager - Loading Time

Similar Messages

Maybe you are looking for