# Queue Performance and Usability

The Queue screen lists the samples that are queued for a step, and provides a table from which samples are selected for placement into the Ice Bucket.

By default, samples listed in the Sample table are grouped by container. Groups are collapsed by default and can be expanded as required by selecting the arrows.

Lab scientists can also choose to group samples by project, submitted sample, or previous step.

### Performance and Usability

In the past, some performance and usability issues were encountered when viewing large data sets in the Queue screen. Clarity LIMS now includes performance enhancements that speed up the Sample table loading time, allowing users to more quickly interact with the data.

Clarity LIMS development teams measured the performance for various samples that are queued for a step with the Time to Interactive (TTI) metric. This metric defines the time it takes for a page to become fully interactive and for functionality to start working (eg, selecting, scrolling, and so on). The metric numbers vary based on the following information:

* Server specification.
* Amount of data stored on the server database.
* Client hardware specifications and the browser type used to access Clarity LIMS.
* Network conditions between the server and client.

### Performance Test Setup

The following table shows the server and client specifications used for the performance test.

The different client types are used to demonstrate the different setups.

<table><thead><tr><th width="132">Hardware</th><th width="259">Specification</th><th>Additional Notes</th></tr></thead><tbody><tr><td>Server</td><td><p>3.1 GHz Intel Xeon Platinum processor (8-core)</p><p>32 GB RAM</p><p>Oracle Linux v8.8</p><p>PostgreSQL 15.2 database</p></td><td><p>The server database is loaded with the following information:</p><ul><li>200,000 submitted sample records</li><li>2,000,000 derived sample records</li><li>500 projects</li></ul></td></tr><tr><td>Client A</td><td><p>3.1 GHz Intel Xeon Platinum processor (8-core)</p><p>32 GB RAM</p></td><td>Access Clarity LIMS within the same network in the lab.</td></tr><tr><td>Client B</td><td><p>2.3 GHz Intel Core i9 (8-core)</p><p>32 GB RAM</p></td><td>Access Clarity LIMS on the cloud. The VPN access and different network region setup results in high network latency and demonstrates the worst case for performance.</td></tr></tbody></table>

### Performance Test Results

The following tables show the results of two performance tests conducted on a Clarity LIMS system on which performance enhancements had been implemented. In both tests, samples were grouped by container.

The tables show how the usability rating changes as the number of samples in the queue increases.

#### Test 1: Container = Tube

Test 1 Performance Results

<table><thead><tr><th width="203">Number of Samples</th><th>Response Time (seconds) - Client Type A Response Time (seconds) - Client Type B 1000</th><th>Response Time (seconds) - Client Type B</th></tr></thead><tbody><tr><td>1000</td><td>2.0</td><td>4.5</td></tr><tr><td>3000</td><td>2.5</td><td>5.0</td></tr><tr><td>7000</td><td>3.5</td><td>6.5</td></tr><tr><td>10,000</td><td>5.0</td><td>7.5</td></tr><tr><td>15,000</td><td>7.0</td><td>10.5</td></tr><tr><td>20,000</td><td>9.0</td><td>12.5</td></tr></tbody></table>

#### Test 2: Container = 96 well plate

Test 2 Performance Results

<table><thead><tr><th width="203">Number of Samples</th><th>Response Time (seconds) - Client Type A Response Time (seconds) - Client Type B 1000</th><th>Response Time (seconds) - Client Type B</th></tr></thead><tbody><tr><td>1000</td><td>2.0</td><td>4.5</td></tr><tr><td>3000</td><td>3.0</td><td>5.5</td></tr><tr><td>7000</td><td>5.0</td><td>7.5</td></tr><tr><td>10,000</td><td>7.0</td><td>9.5</td></tr><tr><td>15,000</td><td>9.5</td><td>12.5</td></tr><tr><td>20,000</td><td>12.5</td><td>15.0</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.connected.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/clarity-lims-v6.3-reference-guide/system-performance/queue-performance-and-usability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.