Performance improvements
BIMQ is a cloud-based data management software that enables different users to access current data at the same time and regardless of location. This must ensure that the data is available to all users in the same quality and consistency. Access to a data status in real time can, depending on the server load, have a negative effect on performance. This is usually made clear by a slower page loading. The BIMQ development team is constantly working on improving and optimizing server performance. Basically, the larger the project guideline, the more data must be validated. The size of the project therefore has a direct impact on the speed. However, there are ways in which the performance in BIMQ can be improved. These will be explained below.
Column reduction
One of the easiest ways to increase the speed of page loading in BIMQ is to reduce the number of columns. The fewer columns that are displayed, the less data needs to be verified. For this reason, it is recommended that you only activate the columns that are actually required.
Displaying the various combinations of project phases and use cases also requires more resources. Here, too, only the necessary combinations should be activated.
Search & Filter optimization
The speed at which the page is displayed can be optimized in two different ways for the area Search & Filter.
1. Adjustment of Hits per Page:
The hits per page can be adjusted in the function bar Requirement Table. The selection indicates how many components are displayed in the BIMQ user interface view. This setting can also be combined with the functional area Search & Filter. The displayed filter results are therefore also limited to the Hits per Page. The lower the number entered, the faster the page will be loaded.
2. Refinement of Search & Filter requests:
With the classic search and filter function, a specific definition is searched for in the database. The performance in this area can be significantly improved through specifications. In the first step, the filter results should be limited to a higher hierarchical level or a discipline model. This means that the search query is only carried out for the selected area and no longer for the entire database. In the second step, the search can be refined further. For example, the search term can be specified by filtering by type (Properties, Groups, Elements ...) or the advanced options (required component, not required components ...). The data query can thus be limited to a specially defined area and thus has a positive effect on the performance.
Optimization of the requirements view
Particularly large project guidelines with several defined combinations of requirements from project phases and use cases lead to increased database queries and thus to increased server load. The requirements are displayed directly on the property level, but also indirectly on the object and group level. The performance can be significantly improved at this point if the aggregation at object and group level is dispensed with. If this is desired, the option: "Show requirement settings on object and group level" must be deselected.
As a result, in the area Project Requirements, the requirement combinations are displayed without aggregation at the object and group level. The following figure shows the view after deselecting the checkbox: "Show requirement settings on object and group level"
However, this checkbox is activated in the BIMQ presetting. The following figure shows the view in the area Project Requirements with an aggregation at object and group level.
This can be clearly recognized by the tick symbols on a gray background.
