Performance is not as expected

[t2gran]

Expected behavior

After switching from plain range-raptor to multi-criteria-range-raptor and at the same time starting to use the dynamic search window the performance degrade was considerable. Many times slower. We did a short test setting the latest-arrival-time in addition to earliest-departure-time and saw the performance improve in one case from 3-4 seconds to under a second.

So first, this task is to investigate and try to find the reason why we at Entur had such a downgrade in performance.

[t2gran]

We should be able to monitor performance in OTP, especially trip queries. At the REST API this can be done with tooling, but with the GraphQL APIs we might have to collect information and provide a REAT endpoint for get it.

We would like to do something similar as Spring does. https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html#actuator.metrics.supported

One option is to use Micrometer lib:

<dependency>
            <groupId>io.micrometer</groupId>
            <artifactId>micrometer-core</artifactId>
            <version>1.7.2</version>
        </dependency>
        <dependency>
            <groupId>io.micrometer</groupId>
            <artifactId>micrometer-registry-prometheus</artifactId>
            <version>1.7.2</version>
        </dependency>

[leonardehrenfried]

I've used the following library before and was satisfied with it: https://metrics.dropwizard.io/4.1.2/getting-started.html

[leonardehrenfried]

There is also a forwarder for prometheus: https://www.robustperception.io/exposing-dropwizard-metrics-to-prometheus

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days