Karisma Network Requirements

Size: px

Start display at page:

Download "Karisma Network Requirements"

Norah Ramsey
5 years ago
Views:

1 Karisma Network Requirements

2 Introduction There are a number of factors influencing the speed of the Karisma response rates of retrieving data from the Karisma server. These factors include the hardware resources of the workstation running Karisma, the Karisma application server and, in particular, the Microsoft SQL Server. This document will focus on the networking requirement of Karisma and will assume that the all other variables are optimal; however a bottle neck in any of these other factors will result in high response times regardless of the network over which Karisma is operating. Disclaimer: This document outlines the Karisma network traffic and indicative network utilisation and saturation points assume no other traffic over the network. For most organisations this will not be the case and the non-karisma network utilisation, such as internet access, and PACS needs to be considered and the network requirements scaled up accordingly. Reviewed by: Gavin Morris, Application Architect Approved by: Adrian Russell, Systems Operation Manager Date: 1 st June, 2007 Page 2 of 11

3 Networking Requirements The fundamental equation for specifying network requirements is: Response time = Amount of data to be transferred / Maximum available data transfer rate Response time The response time is the amount of time, usually measured in seconds or fractions of a second for the data to be transmitted over the network and to the client s workstation. Karisma displays the results to the user after all the data is received. Amount of data to be transferred The amount of data to be transferred from the Karisma client application to and from the Karisma server depends on the functionality performed. Karisma is built on a 3 tier architecture which provides an excellent platform for low data transfer requirements. The table below summarises representative data size transfer for common functionality in Karisma. Data amounts are expressed in bytes (B), and multiples thereof, such as kilobytes (KB equals 1024 bytes), megabytes (MB equals 1024 kilobytes), gigabytes (GB equals 1024 megabytes) and so on. Maximum available data transfer rate The time it takes to push the amount of data from the server to the client (and vice versa) depends on how thick the pipe is connecting the two. The available bandwidth to Karisma is the amount of bandwidth supplied by your network administrator or, if over the internet, by your internet service provider (ISP) less the amount of bandwidth used by other applications. The following are some of the biggest known causes of bandwidth utilisation by other applications (other than Karisma): PACS PACS systems move very large images around the network and can easily saturate low bandwidth availability leaving virtually none for Karisma. You should discuss this with your PACS vendor to determine other options, such as prefetching during quiet/night times and compression methods. Copying files over the network Moving large files through Windows Explorer, MS- DOS, FTP or other means will have similar impact as a PACS system. Internet usage Sites that need to communicate over the internet to access the Karisma server are dependant on other users internet usage using the same bandwidth, as well as the general internet traffic to and from the Karisma server. You should assess and restrict internet usage when Karisma is sharing the same route/isp line. Other applications other applications using the local area network (LAN) or wide area network (WAN), usually over the internet, may impact the Karisma response times if the Karisma data has to wait for the other applications traffic. In environments where a WAN link is shared by multiple applications, it might be necessary to implement a bandwidth management solution to ensure all applications perform at an acceptable level. Maximum data transfer rate is usually measured in bits per second (bps), and multiples thereof, such as kilobits per second (kbps, equals 1000 bits per second 1 ), megabits per second 1 There is much discussion and literature as to the correct definition of kilobits per second (kbps). Some ISP providers use the SI unit where 1000 bits per second equals a kbps while others use similar to converting bytes to kilobytes where Page 3 of 11

4 (mbps, equals 1000 kilobits per second), gigabits per second (gbps, equals 1000 megabits per second) and so on. 1 byte is equal to 8 bits. Throughput versus goodput Your network administrator, ISP and Windows workstation will all indicate the throughput of a connection. Throughput is the amount of bits per second the connection provides, such as 100 mbps (typical LAN). Not all of this is available to transmit data however as the data has to be broken down every 1500 bytes into network packets. Each network packet requires 20 bytes of IP header and 20 bytes of TCP header information (containing the IP address of sender and recipient and other error checking information about the data to ensure it is transmitted correctly). Packets transferred over the Ethernet also impose a 38 byte overhead per packet. This is known as protocol overhead. Therefore the available throughput, or goodput, for transmitting data over a 100 mpbs LAN is approximately: 1460/1538 * 100 mbps = mbps or MB per second (as 1 byte = 8 bits). Approximate goodput of common bandwidth throughput 2 ISP quoted bandwidth (throughput) Approximate bandwidth available to transfer data (goodput) 1000 mbps = 1 gbps MB per second 100 mbps MB per second 10 mbps MB per second 4 mbps KB per second 2 mbps KB per second 1 mbps KB per second 512 kbps 60.7 KB per second 256 kbps 30.4 KB per second 128 kbps 15.2 KB per second Other factors that may affect goodput are: Retransmission of lost or corrupt packets Collision detection 1024 bits per second equals a kbps. The calculations in this document have used SI conversion (1000 bits per second equals a kbps). You should speak to your ISP provider and/or network provider to determine the exact number of bits per second. 2 There are a number of ways to calculate goodput from throughput. The formula used here is the accepted calculation as published on Wikipedia. Page 4 of 11

5 Latency Latency is the amount of time taken between sending a packet and receiving the respective packet acknowledgment back from the receiving workstation. Latency is usually measured in milliseconds. The perceived speed or responsiveness of an application is directly related to the latency of the network, more so than throughput when the network is not saturated. The recommended latency of a network for Karisma is < 100 ms. Firewalls Firewalls are designed to block access to internal networks. Any Karisma access required outside a firewall will require a rule on the firewall allowing the traffic through. It is required that a firewall access rule is provided to all traffic going to and from the Karisma service (CMSService.exe) on the application server through port 40100, where there is a requirement to access Karisma outside the firewall. Page 5 of 11

6 Sample Karisma network utilisation The table below indicates data transfer rates assuming all bandwidth is available to Karisma. Kestral benchmarks all responses to occur within 2 seconds with the exception of variable length data such as reports, scanned request forms and digital dictations. The data for these concepts are controlled by the user and will vary based on length of report, resolution and quality of scanned request forms and length of dictations. The data below does not include time to display the records by the workstation as that is variable for each client and is <1 second on minimum workstation specifications supplied by Kestral. The table below indicates that sites on: 1 Mbps bandwidth could support up to 5 users 2 Mbps bandwidth could support up to 10 users 4 Mbps bandwidth could support up to 20 users 100 Mbps bandwidth could support up to 500 users providing scanned request forms, dictations and reports were < 300 KB and assuming no more than one fifth of the users were downloading or uploading these at a time. Bandwidth < 1 Mbps could be supported however users may experience delays of > 2 secs when scanning, dictating or uploading/printing/downloading large reports. Similarly, document designs with large graphic images may impact distribution preview and printing times. Similarly, retrieving large record sets, for example retrieving hundreds of patients starting with Smith instead of limiting search with filtered criteria, will also increase the amount of data required to transfer between the server and client and therefore increase transfer times. Times that are within the 2 second benchmark are coloured green, while those times that exceed a transfer rate of greater than 2 seconds are coloured red. NOTE: Dictation uploads are performed in the background allowing the user to continue reporting and dictating next report. The user does not have to wait for the upload to finish.

7 Karisma network utilisation table Test Logging On Data to/from CMSConsole and CMSService 3 Sent (KB) Received (KB) Sent Network bandwidth times to transfer data 100 Mbps 4 Mbps 2 Mbps 1 Mbps Received Sent Received Sent Received Load log on dialog <1 <1 <1 <1 <1 <1 <1 <1 Log on to Home page <1 <1 <1 <1 <1 <1 < Patients page Search for patient display patients grid Edit existing patient details Save new or existing patient details details notes reports film bags summary host Requests page requests grid Sent Received /patient 4 <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 <1 0 0 <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < /report 5 <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < /request 7 <1 <1 <1 <1 <1 <1 <1 <1 Edit existing request <1 <1 <1 <1 <1 <1 <1 <1 3 Via server port Patient details all fields populated, general, accounting, medical alert and registration notes each had 84 words over 2 paragraphs. 5 Report details 439 words, 2 bold/underline headings, 6 paragraphs 6 Film bag 2 film bags allocated to patient 7 Request details all fields populated, 2 exams, clinical and scheduling notes each had 84 words over 2 paragraphs

8 Save existing or new <1 <1 <1 <1 <1 <1 <1 <1 request Display request detail <1 <1 <1 <1 <1 <1 <1 <1 Display request notes <1 <1 <1 <1 <1 <1 <1 <1 Display request <1 <1 <1 <1 <1 <1 <1 <1 summary Display request <1 <1 <1 <1 <1 <1 <1 <1 reports /report Display request film <1 <1 <1 <1 <1 <1 <1 <1 bags View request price <1 <1 <1 <1 <1 <1 <1 <1 Requests Scanned images Display request forms <1 <1 <1 <1 <1 <1 <1 <1 1 st image (72 KB 75 dpi) Display request forms <1 <1 <1 <1 <1 <1 <1 <1, next image button 2 nd image (228 KB 150 dpi) Display request forms <1 <1 < < <1 4.13, next image button 2 nd image (489 KB 240 dpi) Insert request form <1 <1 <1 <1 <1 <1 <1 <1 (72 KB 75 dpi) - no preview Insert request form <1 <1 <1 <1 <1 < <1 (228 KB 150 dpi) - no preview Insert request form (489 KB 240 dpi) - no preview <1 < < < <1

9 Preview request form <1 <1 <1 <1 <1 <1 <1 <1 (72 KB 75 dpi) Preview request form <1 <1 <1 <1 <1 <1 < (228 KB 150 dpi) Preview request form <1 <1 < < < (489 KB 240 dpi) Patient exams page Display exams for <1 <1 <1 <1 <1 <1 <1 <1 request grid /exam Display Commence <1 <1 <1 <1 <1 <1 <1 <1 exam steps dialog Save exam steps <1 <1 <1 <1 <1 <1 <1 <1 dialog Display exams details 0 0 <1 <1 <1 <1 <1 <1 <1 <1 Display exams reports <1 <1 <1 <1 <1 <1 <1 <1 Display exams <1 <1 <1 <1 <1 <1 <1 <1 summary Display Cancel <1 <1 <1 <1 <1 <1 <1 <1 examination steps dialog Save Cancel <1 <1 <1 <1 <1 <1 <1 <1 examination steps dialog Reports page Display existing <1 <1 <1 <1 <1 <1 <1 <1 patient reports grid /report Display report notes <1 <1 <1 <1 <1 <1 <1 <1 Edit existing report <1 <1 <1 <1 <1 <1 <1 <1 contents panel Edit empty report <1 <1 <1 <1 <1 <1 <1 <1 contents panel Report details dialog Display forms dialog <1 <1 <1 <1 <1 <1 <1 <1

10 no forms exist Display forms dialog <1 <1 <1 <1 <1 <1 <1 <1 (72 KB 75 dpi) Display forms dialog <1 <1 <1 <1 <1 <1 < next image (228 KB 150 dpi) Display forms dialog <1 <1 < <1 <1 < next image (489 KB 240 dpi) Display dictation 0 0 <1 <1 <1 <1 <1 <1 <1 <1 panel Save report no <1 <1 <1 <1 <1 <1 <1 <1 dictations Display report history <1 <1 <1 <1 <1 <1 <1 <1 panel 1 report history Dictations/transcriptions Display empty Dictate <1 <1 <1 <1 <1 <1 <1 <1 selected report dialog Save empty report <1 <1 <1 <1 <1 < <1 with 30.0 sec dictation Save empty report <1 <1 <1 < < <1 with 60.0 sec dictation Save empty report <1 < < < <1 with sec dictation Transcribe selected <1 <1 <1 <1 <1 <1 < report 30.0 sec dictation Select next dictation <1 <1 <1 <1 < < sec dictation Select next dictation <1 <1 < < < sec dictation Worklists Patient <1 <1 <1 <1 <1 <1 <1 <1 worklist no preview /patient 0 0 <1 <1 <1 <1 <1 <1 <1 <1

11 worklist details tab preview worklist patient tab preview worklist patient notes tab preview worklist report contents (empty report) tab preview Display Arrive patient dialog Save Arrive patient dialog Display Depart patient dialog Save Depart patient dialog <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 < <1 <1 <1 <1 <1 <1 <1 <1

Workfront DAM Performance Evaluation

Workfront DAM Performance Evaluation workfront.com +1.866.441.0001 +44 (0)845 5083771 1 Table of Contents INTRODUCTION) 3! DATA)RATE)VALUE)DESCRIPTIONS) 3! CONNECTION)SPEEDS)&)DATA)TRANSFER)RATES) 3! FILE)SIZE)&)DOWNLOAD)SPEEDS)