starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

long netbox page load time #5312

New Issue
Closed
opened 2025-12-29 19:26:32 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:26:32 +01:00
Owner
Copy Link

Originally created by @sgelineau17 on GitHub (Sep 3, 2021).

NetBox version

v3.0.1

Python version

3.9

Steps to Reproduce

Compared Netbox in version 2.11.12 versus version 3.0.1

Expected Behavior

Optimisation

Observed Behavior

Hello,

I have a Netbox server in production which is in version 2.11.12. I also have a qualifying Netbox server which is in version 3.0.1. The qualification server is a production copy, it has just been updated, the characteristics of the VM are identical.

Version 3.0.1 is much longer to find than version 2.11.12.

Both servers are on a fully up-to-date CentOS 8 basis.

The production Netbox server runs Python in version 3.7 and the production Python 3.9 server.

I give you screenshots of a loading of the Prefixes tab with the debug on the network tab.

Netbox-Prod

Netbox-Qualif

Originally created by @sgelineau17 on GitHub (Sep 3, 2021). ### NetBox version v3.0.1 ### Python version 3.9 ### Steps to Reproduce Compared Netbox in version 2.11.12 versus version 3.0.1 ### Expected Behavior Optimisation ### Observed Behavior Hello, I have a Netbox server in production which is in version 2.11.12. I also have a qualifying Netbox server which is in version 3.0.1. The qualification server is a production copy, it has just been updated, the characteristics of the VM are identical. Version 3.0.1 is much longer to find than version 2.11.12. Both servers are on a fully up-to-date CentOS 8 basis. The production Netbox server runs Python in version 3.7 and the production Python 3.9 server. I give you screenshots of a loading of the Prefixes tab with the debug on the network tab. ![Netbox-Prod](https://user-images.githubusercontent.com/61157268/132033250-5da10380-759c-4d68-b1a7-7e85b9cb7bdf.png) ![Netbox-Qualif](https://user-images.githubusercontent.com/61157268/132033052-324b208c-32ab-4a64-8940-312650536982.png)
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:26:32 +01:00
adam closed this issue 2025-12-29 19:26:32 +01:00
adam commented 2025-12-29 19:26:32 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 3, 2021):

Testing on internal test instances, I see a lower load time on v3 then on v2 for the prefixes with a larger number of prefixes.

Could you provide more information? I see 572 prefixes listed on the v3 instance but no prefixes are displayed, likewise the v2 instance has no prefixes displayed.

Can you provide the following information for each instance:

  • Prefix count
  • VRF count
  • Tenant count
  • Site count
  • IP Address count
  • Column configuration (displayed columns)

These all can have an impact on load times.

@DanSheps commented on GitHub (Sep 3, 2021): Testing on internal test instances, I see a lower load time on v3 then on v2 for the prefixes with a larger number of prefixes. Could you provide more information? I see 572 prefixes listed on the v3 instance but no prefixes are displayed, likewise the v2 instance has no prefixes displayed. Can you provide the following information for each instance: * Prefix count * VRF count * Tenant count * Site count * IP Address count * Column configuration (displayed columns) These all can have an impact on load times.
adam commented 2025-12-29 19:26:32 +01:00
Author
Owner
Copy Link

@Sislik commented on GitHub (Sep 3, 2021):

Netbox 3.0.1 python 3.9, centos 7 loading 63547 IPs (DB size is 260 MB)
image

Netbox 2.10.4 python 3.6, centos 7 loading 63547 IPs (DB size is 769 MB)
image

same DB backend servers, upgraded clone of web server. In generic the 3.0 is way faster than older version and upgrade reduced the DB size quite a lot.

@Sislik commented on GitHub (Sep 3, 2021): Netbox 3.0.1 python 3.9, centos 7 loading 63547 IPs (DB size is 260 MB) ![image](https://user-images.githubusercontent.com/64298143/132049141-27b768cc-4de2-4e08-9b81-aa8e0dd18453.png) Netbox 2.10.4 python 3.6, centos 7 loading 63547 IPs (DB size is 769 MB) ![image](https://user-images.githubusercontent.com/64298143/132049224-feb6af3f-1fa1-411c-abf4-46ee6174a951.png) same DB backend servers, upgraded clone of web server. In generic the 3.0 is way faster than older version and upgrade reduced the DB size quite a lot.
adam commented 2025-12-29 19:26:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 3, 2021):

Let's take a few steps back here. Pasting screenshots from your browser is not going to work. You're also randomly using v2.10.4 above whereas your initial report was for v2.11.12.

First, you need to set up two instances of NetBox (one running v2.11.12 and one running v3.0.1) with the same exact data and configuration. This is crucial to identifying a reliable baseline.

Then, once those have been set up, you'll need to use a tool like curl to make the actual HTTP requests. There are myriad factors which may impact the performance of a general purpose web browser, and we need to isolate as many of those as possible. curl works great for this because it's a very low-level tool, and we can call it with time to get exact measurements. For example:

$ time curl https://netbox/ipam/ip-addresses/

It's best to run each request a number of times and take the average. Then you can compare measurements between the two installations.

@jeremystretch commented on GitHub (Sep 3, 2021): Let's take a few steps back here. Pasting screenshots from your browser is not going to work. You're also randomly using v2.10.4 above whereas your initial report was for v2.11.12. First, you need to set up two instances of NetBox (one running v2.11.12 and one running v3.0.1) with the **same exact data** and configuration. This is crucial to identifying a reliable baseline. Then, once those have been set up, you'll need to use a tool like `curl` to make the actual HTTP requests. There are myriad factors which may impact the performance of a general purpose web browser, and we need to isolate as many of those as possible. `curl` works great for this because it's a very low-level tool, and we can call it with `time` to get exact measurements. For example: ``` $ time curl https://netbox/ipam/ip-addresses/ ``` It's best to run each request a number of times and take the average. Then you can compare measurements between the two installations.
adam commented 2025-12-29 19:26:33 +01:00
Author
Owner
Copy Link

@Sislik commented on GitHub (Sep 3, 2021):

@jeremystretch I'm different user :) so there is just original post and my example, that there is no issue on 3.0.1 and it is way faster in my case with same test he did :)

@Sislik commented on GitHub (Sep 3, 2021): @jeremystretch I'm different user :) so there is just original post and my example, that there is no issue on 3.0.1 and it is way faster in my case with same test he did :)
adam commented 2025-12-29 19:26:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 14, 2021):

Closing as there has been no further response from the poster.

@jeremystretch commented on GitHub (Sep 14, 2021): Closing as there has been no further response from the poster.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: revisions needed type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5312
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?