LAPIS
LAPIS copied to clipboard
An API, a query engine, and a database schema for genomic sequences; currently with a focus on SARS-CoV-2
Opening the [CoV-Spectrum landing page](https://cov-spectrum.org/explore/Switzerland/AllSamples/Past6M), the website sends 19 requests to the `/sample/aggregated` endpoint. In all cases, the client has to wait >100ms for the server response, sometimes even over...
The Chrome dev console pointed me to the Server Timing API ([web.dev](https://web.dev/articles/custom-metrics?utm_source=devtools#server-timing-api), [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Server-Timing)). It looks very useful, should we implement it? Chrome dev console screenshot 
When running `docker logs lapis-lapis-open-1 | grep "9e45aa8e-3bdf-4ff0-a4b7-03eec0419b18"` the output can look like this: `Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_bellsoft-liberica/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -XX:ActiveProcessorCount=64 -XX:MaxDirectMemorySize=10M -Xmx318690624K -XX:MaxMetaspaceSize=98983K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics -Dorg.springframework.cloud.bindings.boot.enable=true line...
The `/sample/info` endpoint on the production server is quite slow and needs >600 ms. Does anyone know why?   Request IDs: - 1412b2a2-6e45-4702-93d0-fe7dafa99d71 - 4082e46e-ee4b-49f7-855d-618f5ad71f9c - 82a550e1-802c-4221-8b83-4098e498b467 - c72c24f2-ae34-45aa-a174-91e047346889...
 Currently, the insertions show up as plain fields. This should not be the case. Instead offer some support for writing queries with valid insertions and mutations.
Targets #374 Needs full dataset on testserver #371. This needs SILO to import data from ndjson
Calling `/sample/aggregated?doesNotExist=123` returns the error: ``` { "error": { "type": "about:blank", "title": "Bad Request", "status": 400, "detail": "'doesNotExist' is not a valid sequence filter key. Valid keys are: " },...