I sometimes notice that, too. Especially when I left DVDP running but haven't used it for a while and then return to it and try to use it.

My guess would be that it's the Delphi environment (the language in which DVDP was written) and its memory management that causes this.

The problem of memory space and its allocation has been the proverbial problem of stuffing 10 pounds of you know what in a 5 pound bag.

I have over 16,000 profiles and if I perform a function that requires scanning the whole db for something, well I might as well go get a cup of coffee.

When you see a computer in an old movie and the tapes are spinning back and forth those tapes are being used as an extension of memory. The UNIVAC I, my first computer only had 1K of memory.

There never is nor will there ever be enough memory. And even if you have a 64 bit PC and Win 7 Ultimate 64 bit operating system and many gigs of memory which I have, many programs are only programed to operating in 32 bit mode. The DVD Profiler is one. It would require two versions of the DVD Profiler, the current version and 64 bit version. Even with all that, if a program goes idle or other programs are running at the same time there will be a certain amount of swapping of data/programs to disc.

If you programming at the operating system level, it something you always have to be aware of. Example when I did the war games computer for USAF, SAC I had to worry about memory space. I had a number network and other computers feeding data. the data had to be written to disc and tape backup and a transaction processing system. One PhD in math who obliviously never did anything in real time, said oh just read a whole message into memory. I showed her that the message format could allow 256 bites per segment, 256 segment per page and 256 pages, that over 16M bites. I explained to her even if they say a message will never be that large, I told her, that is what the format allows and if somebody screws up and I don't plan for it the system crashes and I don't think you want to happen in time of a crisis when you're tracking missiles and planes.

I have a modest collection of only 1400 titles ..( only the best titles for me..,as I'm very particular on what I want to add next )  and with  that being said .: . Even If I leave profiler running in the background it too is very sluggish when I go to resume an operation... But when it is first 'fired up' it runs very fast and no problems with my memory resources.. ( 966 MB (1 GB) available/XP pro ) .. My trick is too get in find what I need or want to do-  and when finished,  shut  Profiler down..

If I leave it open and running , a long time, it doesn't respond as well as it does primary .........

Quoting widescreenforever:

Quote:
My trick is too get in find what I need or want to do-  and when finished,  shut  Profiler down..

If I leave it open and running , a long time, it doesn't respond as well as it does primary .........

That's pretty much my experience also, and it just seems silly that it should take longer to wake up an instance of Profiler that has been inactive than it takes to start it from scratch.

I have never experienced any of these problems, however my collection is a bit smaller

1800 profiles

Windows 7 Home Premium 64-bit 8GB RAM

I actually just left profiler open all night long, does not appear to be sluggish at all, a quick look at task manager shows it only using about 200MB of memory.

I wonder if giving the process a higher priority would help things a bit.

I am small taters, at only 850 ish profiles ( not really counting season DVD disccounts )

I get a slight pause when I go back to the app, but mine typically takes up about 178-500mb and this is with the headshot database loaded up.

-Robert

It's possible that it was designed this way to keep things from getting out of hand for people who run with less memory.

Late update:

It turns out that the answer to the question in the subject is that it really is a Windows problem. Sort of.

I use an application launcher called TurboLaunch. I like it because it keeps me from cluttering my desktop with a lot of icons.

For some reason, I ran into problems with one add-in when starting Profiler from TurboLaunch, but I found a work-around. I started it indirectly but adding it as a task in Windows Task Scheduler and adding a shortcut to the task scheduler in TurboLaunch. That worked fine. Or so I thought. And I forgot all about it.

But then one day I started Profiler from the start menu, and I didn't see these long delays. Some delays, yes, but not nearly as bad as before.

Now I kick myself for not thinking of testing this before. It just never occured to me that starting a program via the task scheduler would change the memory allocation characteristics. Go figure...