timeseries/recent endpoint is much slower than the /timeseries endpoint

[david-a-ries]

I was planning on using the /timeseries/recent endpoint to create some tables of the latest values from various timeseries. The problem I'm facing is that the /timeseries/recent endpoint is significantly slower (10+ seconds for a response) than the regular /timeseries endpoint (under a second for a response). I'm not sure what's happening under the hood but I'm not using category-id or group-id for the /timeseries/recent endpoint (only asking for 1 timeseries). There's two urls below (one for recent and one for just timeseries) for an example of what I'm seeing.

timeseries/recent: https://cwms.sec.usace.army.mil/cwms-data/timeseries/recent?office=NWDP&ts-ids=MLKW.Flow.Inst.15Minutes.0.USGS-REV

timeseries: https://cwms.sec.usace.army.mil/cwms-data/timeseries?name=MLKW.Flow.Inst.15Minutes.0.USGS-REV&office=NWDP&unit=EN

[david-a-ries]

Additionally, the timeseries/recent endpoint does work in swagger-ui; however, it fails to load data when pasting the url into a new tab giving back

{"message":"No Format for this content-type and data type : (application/xml, cwms.cda.data.dto.RecentValue)","incidentIdentifier":"-2091523741094647459","details":{}}

[zack-rma]

From poking at this endpoint, it is slower to respond than a standard timeseries data retrieval, potentially due to the design of the db query.

It also seems that the endpoint is selecting application/xml despite the provided header being application/json on browser queries, but testing via the code does not reproduce the bug. This is what seems to be causing the format error. I'm looking into this to see if I can gather more details on the source of the issue.