...
| Info | ||
|---|---|---|
| ||
Optimizory Technologies is sharing the performance data with users, just as a reference to indicate the level of performance which RMsis is capable of achieving on a specific platform. We provide no warranties with respect to these performance figures, but running RMsis on a server class machine and with a high end Database server, users should be able to achieve higher performance levels. Since the performance depends on many site specific factors, users are advised to base their decisions on system performance at their own sites. Note : These characteristics are applicable to RMsis 1.8.0-r260 and there may be deviations in other versions of RMsis. |
...
Table of Contents
| Table of Contents |
|---|
...
Test Details describe the objectives, assumptions, design and environment of the tests resulting in the performance characteristics shared below.
...
Improvement in rendering time on Browser with 1.8.0
...
- Now the Planned Requirements and Traceability tables are implemented as scroll (large data) tables and hence an increase in number of Requirements in the project will not significantly impact the rendering time.
- All the other tables are paged tables, capable to displaying maximum of 1000 rows in one table. Hence the time taken for rendering is also not expected to increase significantly with increase of data size.
...
...
Performance with Concurrency
...
- This graph shows the average read response time with a mix of concurrent requests at an instant.
- The idea is to determine, how most of the users will experience system responsiveness.
- At the maximum limit, all requests are successfully served without any timeout errors. We perceive that this limit can be pushed further if users are willing to accept response of 15-20 seconds.
...
Functional performance with increasing concurrency level
...
- Worst performing operations, in that order are
- Create / Delete test case at the top of the list, which requires order of all the test cases to be modified
- Create / Delete Requirements at the top of the list, which requires order / hierarchy of all the Requirements to be modified and all currently referenced objects to be updated.
- Indent / Outdent operations, which require modification in Requirement Hierarchy
- Our opinion on the impact of the responsiveness of Create / Delete operations
- Users tend to create new entities at the bottom of list. So the delay will be insignificant in that case.
- Moreover this is the responsiveness for a large project containing approximately 25,000 entities of each type. Such projects are very rare.
- Overall we think that such situations will be rare and most of the users will not be impacted by this dimension.
- Our opinion on the impact of the responsiveness of Indent / Outdent operations
- First of all, impact will be significant only in large projects.
- Users will do well if they avoid bulk operations for Indent / Outdent or at best choose only a few of these for bulk operations.
- Overall we think that such situations will be rare and most of the users will not be impacted by this dimension.
Performance of Light Weight Operations
In the graph below, we observe that the worst case response is well under 15 seconds, even at a concurrency level of 50. So we perceive that the users should feel that the system is fairly responsive for most (90%) of their operations.
...
Functional Performance vs. Project Size
These test cases show the degradation of performance with increasing data size in a project. The details are available at Functional Performance vs. Project Size
...
Memory Bottlenecks
RMsis 1.8.0 was tested for Memory limits and some observations indicate the extent of memory required for a typical instance.
...
Note : Please note that the table shared above is just an indicator for a typical data set and for a specific instance. For another instance, the observations may be different (based on the number of custom fields, relationships, number of issues etc).
| Page Tree | ||||
|---|---|---|---|---|
|
...