|
This topic comprises 2 pages: 1 2
|
Author
|
Topic: Could someone help me with why GDC TMS might have become unbearably slow?
|
Donnacha Kenny
Film Handler
Posts: 8
From: Oak Forest, IL, USA
Registered: Jun 2011
|
posted 04-16-2016 12:31 PM
GDC TMS usually runs fine on our dedicated computer; it could sometimes get sluggish, but even then, reopening the program and/or power cycling would quicken things up again. It would scarcely take a minute to scan the contents of networked projectors (all of which have SX-3000 IMBs) and the local storage, and would not have an issue connecting, managing cpls or anything else.
However, in the past week, it has become utterly unusable. If I'm lucky, selecting anything takes several seconds to be recognized, often with the screen fading to white and becoming unresponsive for several seconds. Sometimes it works, sometimes the program just says (not responding) and stays that way until a forced quit. It's not unusual to right-click on something, wait twenty seconds, see the *shadow* of the right-click submenu, then wait longer, then get the submenu, wait longer, and then be able to select anything off the submenu. And if it recognizes that I've clicked on it? Wait some more. Provided it doesn't fade to white almost instantly.
I spoke to a GDC technician who suggested I upgrade the TMS 3.4 I was using to a later version, TMS 4. TMS 4 installed fine, but would crash as soon as I tried to open it. I uninstalled it and installed the latest version of 3.4 instead, but this did not help and everything was still slow and unresponsive. I was then told to uninstall Postgres and the TMS version I was using so I scould upgrade both, as Postgres would have to be updated too. After installation, Postgres would not start, and I called GDC. From 9pm on Thursday night to 5am Friday morning, two technicians logged in remotely to get Postgres to run and thus get TMS working. The second technician installed TMS 4 instead of the latest version of TMS 3.4. After wiping out all the stored connections and rebuilding the network of projectors, everything should be working fine, but it's still completely slow and unusable.
One might assume it's a lack of memory or dulled performance, but only TMS is being slow. While TMS is running, memory usage is never above 50%, disc activity rarely breaks 10%, and CPU peaks around 6%. Current OS is Windows 10 Pro (I'm told there is no support for TMS with 10, but it wasn't giving me this much grief before this week, and even if it would help I can no longer downgrade to Windows 7), 64-bit, memory is 4GB RAM, Processor is 3.4GHz Intel Core i7-3770 CPU. If that's relevant, please let me know, but remember, no other program is causing me problems, even memory hogs like Google Chrome. Closing out of nonessential programs does nothing to help, nor does restarting or power-cycling. Even on the rare occasions I open Chrome (like I have open now) while TMS is running, Chrome's performance is unhindered, so it's doubtful the resources are the issue.
I tried ingesting trailers off a CRU drive earlier. It took half an hour to populate the contents to show me what I could ingest, and then when I went to uncheck all, it gave me "not responding".
TMS takes a good half hour at least to boot up, scanning projector drives and local TMS storage and taking forever. It used to take no more than a minute to scan the eight projectors and the local storage. If I use VNC address book I'm able to communicate with the projectors instantly, so it's not an issue with the network.
I ingested keys this morning and the keys were not sent to the projectors, even though the program said they were ingested. Trying to update via TMS gave me (not responding). I had to ingest locally.
The GDC techs have been very eager to help, but their plan always seems to be uninstall and reinstall, so I'm not sure even they can understand what's the story.
This is incredibly frustrating, as you can imagine, and I can't run a business like this. Please advise, as I'm kind of at my wit's end. Thank you.
| IP: Logged
|
|
|
Donnacha Kenny
Film Handler
Posts: 8
From: Oak Forest, IL, USA
Registered: Jun 2011
|
posted 04-16-2016 04:13 PM
TMS is 4.17023. I had been using 3.43631 before the techs uninstalled it and installed TMS 4. Bear in mind, TMS 3.4 was working well, until it wasn't, so it's not a question of downgrading to 3.4. I don't really care what version of TMS we use (4's a bit stupid with its layout, but nothing's perfect) as long as it works.
I'm using a Dell Vostro 470 with Intel Core i7-3770 CPU, 3.4 GHz, so that's quad-core. Installed RAM is 4 GB, but TMS never had an issue with running 3.4 with that much RAM and I rarely even use 50% of the available RAM even with several things running. Hard drive is a 500GB 7200RPM Seagate and I'm only using about a quarter of the space. Antivirus software is up-to-date and working. Remember, it's only TMS that's underperforming - everything else is working fine. DCP-o-matic works like lightning on the odd occassion I need it.
SX-3000s are all up-to-date too. No discernible conflicts on my end between the IMBs and TMS before this week.
The GDC techs are going to have another look on Sunday, which is nice, though it doesn't help me too much (not like we're do anything on the weekend at the cinema or anything).
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 2 pages: 1 2
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|