Goldilocks and DPS Server Sizing

For me, one of the best parts of being a Dad is the night-time ritual of putting my son to bed. After giving him a bath, and putting on his PJs, we sit down together and read stories before going to bed. The other night we were reading Goldilocks and the Three Bears. In the story, Goldilocks was testing chairs and tasting porridge, always looking for the right balance between too hard and too soft, too hot and too cold. I couldn’t help but notice the similarities to figuring out how much hardware is required when deploying AutoVue Document Print Services. You don’t want too much hardware or too little. Unfortunately, unlike the story, testing different server setups during an implementation to find this balance just isn’t feasible. If only there was a tool that could help find this magic number of servers (hint: there is… keep reading).

What is Document Print Services

As you may be aware of, AutoVue Document Print Service (DPS) is a solution used to print documents programmatically. DPS is Web Service driven, so users can trigger the printing through their normal work process, instead of having to open up every document to print them. DPS consists of two components: the AutoVue server and AutoVue WebServices, which are each deployed on their own machine.

Scaling DPS – 1 to 1 ratio

Just like AutoVue, DPS can be scaled across multiple servers in order to server more requests. It’s important to scale the AutoVue server and the AutoVue Web Services machines at the same rate. You can think of each DPS instance as a pair of servers consisting of 1 AutoVue server and 1 AutoVue Web Services server. When scaling DPS, it’s important to add complete DPS server pairs. You don’t want to have more AutoVue servers than Web Services servers or vice versa. You want to maintain that 1 to 1 ratio between them.  For example:  if 1 DPS server pair is not enough, you may need 2 DPS server pairs, consisting of 2 AutoVue servers and 2 AutoVue Web Services servers.


How Many Servers

The next big question is how many of these DPS server pairs are required? Deploy too many servers and you’ll have wasted hardware which is expensive to buy and maintain. Deploy too few and you’ll have users wait forever to get their printouts. As in the story of Goldilocks, we want to find the number of servers that is “just right”.

We have just released the AutoVue DPS Sizing Tool to solve this problem (see the screenshot above). The DPS Sizing Tool lets you enter how many files need to be printed every hour, what types of files are being printed, and how big they are. The tool then tells you how many DPS server pairs you need to handle the printing throughput.  Using this tool, you can be sure you will deploy the right number of DPS server pairs the first time, and avoid the pain of a trial and error approach to sizing.

The AutoVue DPS Sizing Tool is available to Oracle partners on the AutoVue Enterprise Visualization Knowledge Zone under the Tools and Resources section of the Sell tab.


Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

The authors of this blog are members of the AutoVue Enterprise Visualization team at Oracle. The views expressed on this blog reflect those of the members and do not necessarily reflect the views of Oracle.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
30
   
       
Today