MartyConnelly
martyconnelly at shaw.ca
Wed Apr 23 11:38:16 CDT 2003
For normal operations, Access, like other RDBMSs has background processing that uses the processing power. The Windows Task Manager usually shows 99 - 100% CPU usage for Access. However, Access will yield CPU to other tasks if required. It just means that there is a constant polling among other things taking place, but Access will yield when appropriate. It takes up CPU time in low priority threads for data caching, etc. Anything you do on the machine, including the screen saver, gets priority. I have seti at home running in the background so my CPU shows 100% all the time, it too runs on a low priority so has little effect on performance. The only bits I would be interested in when monitoring CPU useage would be things running at normal or high priority. Your Citrix hosting guys should look up info on how to display priority and threads. There is KB Access article but it is rather vague as to all the causes mumbling something about keyboard polling but it was wriiten for Access 95. Michael Kaplan is kinda of caustic about this vague explanation about this so called problem. Mark Whittinghill wrote: >Hi all, > > We are delivering a networked app that will be delivered thru Citrix. It >is an A2K FE with mdb BE. Later this year, we will be moving it to SQL >Server with ODBC connections. There may be as many as 50 people logged in >to the app at once, but not nearly that much simultaneous use. The Citrix >hoster was testing it and found that with single user attached, performing a >single query, a dual PIII 500MHz server was hitting the CPU up to 57%. They >are very concerned about this. We have another similar app running for >another client, and it works fine. Does anyone have info about this kind of >processor usage running Access, and how this affects Citrix? I know this >kind of app works, but we could use some hard documentation. Any help is >much appreciated. The client has sent out a highly cc'ed email calling this >a "p***ing contest" between us and the Citrix hoster, which it's not. We >each have our own technical sphere and are just trying to make this project >work. They have a meeting this afternoon, and it would be good to get >something to them by then. > > >TIA, > >Mark Whittinghill >Symphony Information Services >612-333-1311 >mwhittinghill at symphonyinfo.com > >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > > >