Requesting processes very slow

[m-mohr]

Connecting to the VITO back-end is very slow right now.
For me, it takes around 1,5 minutes until the /processes endpoint has fully returned the data.
This is rather annoying, especially in the Web Editor where the processes are requested upfront.

I guess this is due to the mask_scl_dilation being so large? Maybe it would be a good idea to not return the "process_graph" property for pre-defined processes, where this is not very useful anyway.

[jdries]

Right now it's very fast for me, loads in seconds.
Could also have been server load. Can you try again?

[m-mohr]

This is a recurring issue I have for a couple of days (could also been weeks) already, so I'm not having the issue for the first time. It's also still slow right now. Could be that it's a load issue, but then you seem to struggle load issues pretty often?

I've tried only Web. Not sure, maybe it's also not an issue with Python? But at least it also seems slow in the QGIS plugin (but there I have no chance to check what is slow.)

[m-mohr]

@jdries How quick is getting to the Model Builder with this URL https://editor.openeo.org/?server=https://openeo.vito.be&discover=1 for you?

[soxofaan]

For me it's also pretty fast. /processes requests are typically between 0.5 and 1 second

loading that openeo editor page was also pretty fast, the /processes endpoint is indeed the slowest, but not problematic:

[m-mohr]

Hmm, is it then that my connection is too slow? I've tested it on DSL and my mobile connection and both are slow. Strange...

Anyway, maybe it's still a good idea to remove process graphs from pre-defined processes to make initial requests faster? 1 MB for initial discovery seems not ideal.

[m-mohr]

But then the 1.1 MB GEE collections transfer in under a second. Something strange is going on for sure... Are you somehow directly connected to VITO? VPN? Maybe it's just an issue for externals?

[soxofaan]

With or without our VITO VPN doesn't make a difference.

I also tried with https://www.webpagetest.org to test speed from other locations, and it's bit slower (e.g. 2 or 3 seconds from the US), but it's still order of seconds

[soxofaan]

Anyway, maybe it's still a good idea to remove process graphs from pre-defined processes to make initial requests faster?

that's certainly possible (e.g. by default), but there is not standardized way to get the process graph if you want it.
For example with collections you have the "basic metadata" (all collections listing) and "full metadata" (single collection) views, but for pre-defined processes there is only one view: the "all processes" listing.

[m-mohr]

While that is true, for pre-defined processes the use cases where you'd need the process graph seem very limited. With Open-EO/openeo-api#348 you'd get such an endpoint to get the full process description.

Anyway, I've tested connecting to VITO via the university VPN and there it's much faster (like 2 secs). That's not fast, but okay.
I'm really puzzled what makes the request so slow through my internet provider (Telekom) while it works with the same connection just tunneled through a VPN. So speed can't be the issue. Strange...