ITGOD (3/7/2006)I a running a server 2003 environment on a p4 2.4ghz with 1gb of ram and a sata raid 5. Its not really designed to be a server but it has done its job well in the past. I have noticed while using ayanova it usualy takes at least 5 seconds and sometimes up to 15 to open piece of data such as a service workorder or a memo or a parts request etc. I notice similar lag with saving data. I also notice there is about a 10 minute gap between the time i send a memo and the time a notification is sent out to the recipiant. Its not the biggest problem in the world but it gets a little anoying. So what i am woundering is if there are minimal specs for the program? Am i running a fast enough server? Do you have any recomendations as to configurations that may speed up my performance? Any help would be appreciated.
Thanks
David
Hi David, just a couple of points I wanted to make sure we’re clear after reading your post:
Yes that system is, on paper anyway, more than fast enough to run AyaNova. The slowest system we tested on here is a classic Pentium 2 450mhz with 1gb of ram. It’s our baseline system for testing performance on older hardwareand AyaNova on it performsway faster than what you describe on that system. You have a serious bottleneck somewhere there.
Opening a memo should be a split second operation on a local area network. The service work order form is the slowest of any of the forms in AyaNova to open because it has hundreds of controls on it that are selectively displayed or not depending on the type of work order and what you click on as you go through it, but even it should load in much less than 1 second.
Hopefully the troubleshooting steps in the manual that Joyce directed you to will reveal the problem on that count.
The other thing I wanted to make sure was clear is that a notification is not sent immediately when you do an operation in AyaNova that generates a notification. Notifications are created immediately in a waiting table in the database and every 5 minutes the notification processor checks that table and processes accordingly.
On the other end of the notification, if a user is using a popup type notification to receive on in AyaNova it’s also polled about every 5 minutes.
So in theory there can be up to a 10 minute delay between the moment a new notification is generated and the moment it pops up in AyaNova.
The polling delay at the receiving end only applies to popups in AyaNova, if you were to send an SMS notification (for example) then it would pop up on their cell phone or pager as quickly as the cell company takes to process the notification email when they receive it.
The reason there is a 5 minute polling interval in the notification sending process (Generator) is because it’s more efficient to do them in batches. If they are done immediately there is a tremendous potential load put on the whole system be it the database, the email server etc.
The same goes for the popups, every time AyaNova checks for popups it’s not able to do anything else for that split second it takes, so if it checked too often you would see a delay in responsiveness within AyaNova itself as you are using it.