Is ~8 seconds normal for fetching ~1k devices via NetBox API?

[PeterKnotek]

Body:
Hi everyone,

I’m working with a NetBox instance (https://netbox.domain/api/dcim/devices/) and I noticed that fetching around 1,077 devices takes roughly 8 seconds. I tried several variations:

1. Fetch all fields:
   https://netbox.domain/api/dcim/devices/?limit=9999
   real 0m7.805s

2. Fetch only selected fields:
   https://netbox.domain/api/dcim/devices/?limit=9999&fields=site,location,role,name,primary_ip,device_type,custom_fields
   real 0m7.886s

3. Explicit JSON format:
   https://netbox.domain/api/dcim/devices/?limit=9999&format=json
   real 0m8.077s

Even limiting the fields didn’t seem to reduce the response time significantly.

Additional context:
I’m running NetBox on a virtual machine with 4 CPU cores and 6 GB RAM. I noticed that during a GET request for all devices, one core spikes to 100% for a short period, while the others remain mostly idle.

Questions:

1. Is it normal for NetBox to take ~8 seconds to return all devices in one request for this size (~1k devices)?
2. Is there any way to make the API GET request utilize more than one core, or is it normal that a single request is mostly single-threaded?
3. Are there best practices for improving API response time for this scale, or is this expected behavior?

Thanks