Home Forums Discussions Problems Imported items speed

Imported items are becoming terribly slow to load on patients with multiple labs and items. 15 seconds or more is not uncommon.

Assuming the obvious.... fast network, big new server and clients etc.... where do we look?

A post from one of the beta testers suggests 6.5 will default to the folders closed. Will this help, or does everything load even if the folders are closed?

Has the sun popped over the horizon yet up there? I was thinking maybe the frozen tundra may be a factor. Seriously, when I upgraded to 6.3.3 a while back and hardwired my nurses computer it took the lag from 15-20 seconds to 1-2 seconds. You have likely already instituted these changes, and I do not know the answer to you last question.

David,
I was skeptical initially because the "II folders stay closed" feature was implemented a bit differently than I anticipated, but I think it will address your issue (one which has not affected me, but has worried me for a long time).
Once you open II in a given chart, there is an option to keep the folders closed when it is opened in the future. That should prevent all the items from opening (each time in the future, for that one chart).

Thanks to you both. And, yes, Jimmie, it is the equinox. Gaining sunlight at 7 minutes per day!!

David,

What version you on?

Because II accesses external files, it becomes *very* Disk IO dependent.

We are recommending practices move their AC installs to SSDs if performance is an issue, esp. if they use II heavily.

I'm on 6.3.3. The SSD sounds good except for the cost issue of a RAID drive. I may explore it if 6.5 doesn't improve matters. Thanks.

I finally spent the money on tech hardwiring an ethernet cable to my office. Now the II are much faster.

We are hardwired and run a decent server and also experience extended wait times when opening imported files.

We are still on version 6.3.2, does 6.3.3 bring significant advantages over 6.3.2? Do es anyone know when 6.5 is to be released?

Thanks, Oliver

Several posts here suggest that all would be made well by hardwiring everything. However, the II load at exactly the same speed on the hardwired machines as on the wireless. The wiring is all new, Cat6, gigabit switch, and speed has been repeatedly checked and found to be high. The network, does not seem to be the limiting factor, and this leads me to believe it has something to do with the server or program itself. I think Indy has a good idea. I'll check it out.

Just ordered a server from Dell Outlet for a client, and part of what we be doing to "trick it out"* is to add 256G SSD drives, specifically as they have almost 100G in II.

In this particular case, the host system will be either CENTOS or RHEL, but the AC directory will live on the SSD, and I expect they will be impressed with their new "Rocket".

We are also swapping out their 10/100 switches for GIG switches.

*Yes, I realize that "Trick it out" is dated, but I just can't say "pimp" or "bling" with a straight face; call me old-school.

That's when you know you're old school. Even those two are considered old school nowadays haha.

Speaking of Old School, I am just not ready to rely on SSDs for a server.