APPENDIX: P6 Compression Server FAQ

Question #1: How many total concurrent sessions were simulated?

Answer #1: We simulated 200 concurrent sessions with 5 of them being simultaneously and continuously used in processing client requests. The limit of five clients was dictated by the CPU frequency and the amount of data to be compressed.

Question #2: What was performance like under larger loads?

Answer #2: There are two kinds of large loads for P6 Compression Server.

The first type addresses the case of many clients sending Web-like (small) requests, expecting small responses. In this case the compression benefits are minimal (next to none) since there is not enough data to compress. As a consequence of this, the number of requests served simultaneously is limited by the overhead involved in maintaining threads and finding sessions. For the recommended hardware, the limit in this case is between 75 and 100 requests processed simultaneously.

The second type of large load addresses the case of few clients updating or loading large amounts of data through P6 Compression Server (large databases). In this case most of the CPU power is used for compressing the data. For the recommended hardware, the limit is between 5 and 10 requests processed simultaneously.

Question #3: How many users can one P6 Compression Server support?

Answer #3: The number of users depends on the hardware power, most used scenario and the database size. See answers #1 and #2 for details.

Question #4: Is the size of the project a consideration?

Answer #4: Yes. The size of the project directly affects the loading time during open project.

Question #5: How much RAM does each user session require?

Answer #5: The amount of RAM required by one user session is about 64KB. However, the amount of RAM used while processing requests is 10MB on average and can grow beyond 200MB when large blob data is uploaded or downloaded from the database. The 200 MB statement is true only if there are very large blobs (over five MB) in the data.

Question #6: Can multiple P6 Compression Servers be used to support large user populations?

Answer #6: Yes. However, because of the high traffic, each P6 Compression Server requires a dedicated NIC in the database server machine and therefore the number of P6 Compression Servers that can be used could be limited by the Oracle database machine. One of the problems we had was not being able to support massive reads and writes on the same NIC. This could be a problem that could be solved differently by the customer; our approach was to use multiple NIC’s.

Question #7: Does each P6 Compression Server require a dedicated hardware platform or can it host other processes, i.e., P6 Progress Reporter, P6, etc?

Answer #7: P6 Compression Server, when configured and used correctly, requires more than 80% of the CPU power. It is not recommended to run any other CPU intensive applications on the same hardware with P6 Compression Server.



Legal Notices
Copyright © 2005, 2016, Oracle and/or its affiliates. All rights reserved.

Last Published Thursday, September 22, 2016