API call to get the list of node is REALLY slow with latest version
Calling API https://rudder.example.com/rudder/api/latest/nodes is super slow : 15s with 350 nodes
Same call with https://rudder.example.com/rudder/api/4/nodes is only 0,2s
We probably broke something in the latest version
Targetting to 3.0, but I'm not sure of the actual version of latest that is slower
Updated by François ARMAND almost 5 years ago
On an other (more realistic) rudder instance, we have a little difference.
- full lastest (api v6):
time curl -k -H "X-API-Token: ...." -X GET 'https://otherrudder/api/latest/nodes'
0,02s user 0,00s system 1% cpu 0,970 total
- only what was reported in previous api:
time curl -k -H "X-API-Token: ...." -X GET 'https://otherrudder/api/latest/nodes'?include=minimal
0,02s user 0,01s system 2% cpu 0,863 total
- api v5:
time curl -k -H "X-API-Token: ...." -X GET 'https://otherrudder/api/5/nodes'?include=minimal
0,01s user 0,01s system 9% cpu 0,255 total
This is of course higly non-scientific, because data with one try... But we can clearly see a 4x in total time, between API v5 and api v6 (between the two api v6 call, we can guess it's just because there is so much more data returned).
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
- 3.1: Changelog
- 3.2: Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/