If we have multiple users in MES with a 24 hour/ 5 days a week operation, will this clock out impact performance? At any give time you could have up to 10 users in MES and they do clock out at the end of their shift but system still seems slow. Does having employees not clocking out at the end of each day impact performance more than the number of users clocked in the system? For example, we could have five users not clocked out from previous days but up to 20 users clocked in. If we clocked out those five users, would this help with performance on the 20 users?
--- In vantage@yahoogroups.com, "jerrydwein" <jerry@...> wrote:
>
> Hi Kristin/Brian,
>
> You identified the problem. Some of our users were not hitting the clock out button at the end of the day. As soon as I clocked them out, the performance improved dramatically. We're now down to a 1-2 second login times again. Thank you very much for the input.
>
> Jerry
>
> --- In vantage@yahoogroups.com, "Kirstin Brandt" <kirstin.brandt@> wrote:
> >
> > I read the scenario you listed below and had the same question as Brian. Do you clock out at the end of each day? This is different than completing the operation when ending activity or logging out. Check the Clocked In date next to the picture. It should have today's date. You can also check by pulling up the Labor Entry record for one of the employees having a problem. After you enter their employee ID, click on the Payroll Date. The search button should return one record for every day the employee worked.
> >
> > If they are indeed clocking out at the end of the day, do you regularly close your jobs and capture WIP?
> >
> > --- In vantage@yahoogroups.com, "jerrydwein" <jerry@> wrote:
> > >
> > > All of our users clock out of all operations they complete. We verify that their queue only contains operations they are currently working on. Since we track job status, and what operations on a job are completed, we have to have them correctly complete the operations they start.
> > >
> > > Thanks, Jerry
> > >
> > > --- In vantage@yahoogroups.com, "Brian Roberts" <broberts@> wrote:
> > > >
> > > > To emphasis one word below: CLOCK out instead of just log out.
> > > > Otherwise a query intended to pick up just today's jobs from the
> > > > database is returning many months' worth of jobs.
> > > >
> > > >
> > > >
> > > > Brian.
> > > >
> > > >
> > > >
> > > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > > > Of bw2868bond
> > > > Sent: Tuesday, June 19, 2012 6:13 PM
> > > > To: vantage@yahoogroups.com
> > > > Subject: [Vantage] Re: MES Performance Issue
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I have no experience with this personally, but I recall seeing similar
> > > > threads in this group. AFAIK MES login sends job data that the user is
> > > > Active in. I seem to remember if they are clocking out of jobs properly
> > > > then the amount data reduces.
> > > >
> > > > Again, this is what I remember reading......
> > > >
> > > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> > > > "jerrydwein" <jerry@> wrote:
> > > > >
> > > > > I have additional information, we are on Epicor 904.507a. We used
> > > > Process Monitor and Wireshark to find out that the server is sending the
> > > > client a serious amount of data, for some users this is about 5.4M of
> > > > data. It appears the heavier the MES user is, the more data that is
> > > > accumulated and resent to the client from the server. Once a threshold
> > > > is hit, the client hickups on the packets and it takes it a couple of
> > > > minutes to recover. It then retreieves the remaining data.
> > > > >
> > > > > In looking at the data that is being sent to the MES client, it
> > > > appears to be all of the jobs that user has ever touched. What in the
> > > > world is Epicor doing sending all of this data to the MES client when it
> > > > isn't used for anything that I can see?
> > > > >
> > > > > My question is, how can we stop the transfer of this data? is there
> > > > something we can do to flush the system so it no longer sends it to the
> > > > client? In our Options Menu we do not have a way of flushing the Client
> > > > Cache, is there another way of doing this?
> > > > >
> > > > > Any help we be greatly appreciated, we have users who are now
> > > > experiencing 3 minute logins and 2-3 minutes to load the job screen.
> > > > >
> > > > > Thanks, Jerry
> > > > >
> > > > >
> > > > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> > > > "jerrydwein" <jerry@> wrote:
> > > > > >
> > > > > > All systems using MES originally didn't have performance issues. As
> > > > users started bar code scanning more and more, the shop user accounts
> > > > started slowing down.
> > > > > >
> > > > > > We have several shop user accounts that do not have any performance
> > > > issues at all. But, we have a significant number that do, even on the
> > > > same machine.
> > > > > >
> > > > > > There appears to be some cache that is not being cleared or
> > > > something related.
> > > > > >
> > > > > > Thanks, Jerry
> > > > > >
> > > > > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> > > > John Driggers <waffqle@> wrote:
> > > > > > >
> > > > > > > It sounds like what you've got are performance issues rather than
> > > > a bug.
> > > > > > >
> > > > > > > Try the same thing on one of your best workstations, or even
> > > > directly on
> > > > > > > the server. If it runs fine there, you may just need to get a
> > > > better
> > > > > > > machine for your MES workstation.
> > > > > > >
> > > > > > > If it's slow everywhere, it's probably the server/network.
> > > > > > >
> > > > > > > If this is a recent development, check for new BPMs,
> > > > customizations, BAMs,
> > > > > > > etc.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > *John Driggers*
> > > > > > > *High End Dev, System Design, Profit Drinking*
> > > > > > > *
> > > > > > > **:: 904.404.9233*
> > > > > > > *:: waffqle@*
> > > > > > > *:: NO FAXES*
> > > > > > >
> > > > > > > *
> > > > > > >
> > > > > > > *
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jun 13, 2012 at 1:55 PM, jerrydwein <jerry@> wrote:
> > > > > > >
> > > > > > > > **
> > > > > > > >
> > > > > > > >
> > > > > > > > Hi Everyone,
> > > > > > > >
> > > > > > > > We have a single login account that we use to Login to Epicor
> > > > for shop
> > > > > > > > personnel. Then each of the shop personnel has their own
> > > > employee login's
> > > > > > > > to log into MES. Here is a typical scenario with its problems:
> > > > > > > >
> > > > > > > > Step by Step issue that Mike sees:
> > > > > > > >
> > > > > > > > 1. Mike logs into MES using Shop user
> > > > > > > >
> > > > > > > > 2. Mike then logs in with his shop account
> > > > > > > >
> > > > > > > > a. It takes a couple minutes to show up...it hangs and comes up
> > > > > > > >
> > > > > > > > 3. Mike then starts a job
> > > > > > > >
> > > > > > > > a. This again takes a couple minutes before coming up and shows
> > > > the app is
> > > > > > > > non responsive for that period of time.
> > > > > > > >
> > > > > > > > 4. Mike then fills in the fields
> > > > > > > >
> > > > > > > > a. This part seems to function normally
> > > > > > > >
> > > > > > > > 5. Mike then Completes the job
> > > > > > > >
> > > > > > > > a. This functions normally as well.
> > > > > > > >
> > > > > > > > (**NOTE: He seems to see the lag, and like most users, at
> > > > logging in and
> > > > > > > > starting jobs...the other tasks seem to be normal.**)
> > > > > > > >
> > > > > > > > Does anyone know what can be causing this problem.
> > > > > > > >
> > > > > > > > Thanks, Jerry
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>