For you other CPS users, especially in Thin Client enivornments, do you have a policy for the most number of windows to get the best experience?
We are having some issues with our TS enivornment where some users are locking up when they have a lot of schedules open? 10 plus with 7 to 10 resources on each.
We have a mixed environment, so both FAT clients and thin clients. We have noticed that on FAT clients that when users open 4-5 schedules at a time everything starts to bog down. Every additional window slows CPS down to a halt eventually. Thin clients can usually handle 3-4 before I start to notice dramatic performance issues. this is of course depends on Hardware. we run 64-bit OS with 4GB of DDR3 RAM. Thin clients have a 1.4 GHz atom processor and 512MB of RAM
I have advised staff to use the search feature (magnifying glass) when using the Schedule module. It takes less than 5 seconds to click->search->open a new schedule. So only one screen is open We also started having master resource calendars made in case providers being booked were at other sites, or different floors.
-Master
-Department
-Building
-Floor
jdibiasio said:
We have a mixed environment, so both FAT clients and thin clients. We have noticed that on FAT clients that when users open 4-5 schedules at a time everything starts to bog down. Every additional window slows CPS down to a halt eventually. Thin clients can usually handle 3-4 before I start to notice dramatic performance issues. this is of course depends on Hardware. we run 64-bit OS with 4GB of DDR3 RAM. Thin clients have a 1.4 GHz atom processor and 512MB of RAM
I have advised staff to use the search feature (magnifying glass) when using the Schedule module. It takes less than 5 seconds to click->search->open a new schedule. So only one screen is open We also started having master resource calendars made in case providers being booked were at other sites, or different floors.
-Master
-Department
-Building
-Floor
We have a similar policy in place. we have seen some definite issues with speed, crashing etc when users have multiple copies of the schedule open. We use Windows Terminal Services and each user would have 3-4 copies of the schedule open and it would start to slow every one down. Now our users just search for the new date / schedule with the magnifying icon as well, this has helped in that respect.
we also at one time had a confirmation from GE that the schedule component can be a real resource hog depending on how many "resources" are trying to be shown in the schedule at one time. We even still have issues with some users who can not view all active schedules at one time because of the amount of resources it takes.