Hi Joel, Hyland does not have exact documentation on client load on the application server as the load will depend on the use case. Though I can provide you with some information pertaining to stand-alone FOS functionality that may help in proofing out your new solution. The stand-alone FOS client is fairly lightweight when it comes to cross chatter with the server. The amount of network traffic will vary depending on the number of document types that are configured for registration of patients.
On login to the server, the client will pull down information for the document types and keyword types configured for FOS, in addition to any overlay documents or template documents if using templates stored in OnBase. Therefore, the initial connection is probably when FOS is pulling down the most data from the server. If you want to reduce load on the server, I would recommend not closing FOS in between patient registrations and simply minimize the client (which can be configured to automatically happen upon upload if used in conjunction with App Enabler).
During upload of information to the server, the meta data should have minimal impact on server performance and the majority of processing will be uploading the actual document data. As this is a standard feature of the software, network and disk group performance are most likely a bigger concern at this point than the load of the application server. But again, this will depend on the number of users/workstations using FOS per application server with a given departmental FOS configuration file and can be better analyzed in your own test environment(s).
More important factors to consider that are indirectly related to FOS are various amounts of processing on the document type level during document archival/upload that the application server may need to perform. This includes auto-foldering and workflow processing that may execute while the document is being stored and can make it appear as if uploading a document from FOS is causing high load on the server. That will depend on how efficient those solutions are implemented within each environment. Hopefully this information can aid in rolling out your new solution.
Thanks,
Tommy
